Lines Matching refs:user

20     CXL provides a mechanism by which user space applications can
23     user space application direct access to Flash storage.
29     special path for user space access, and performing error recovery. It
40           user space with a special block library. This mode further
55     directly in each user I/O, but at the minimum is involved in the
56     initial setup before the user application is allowed to send requests
86     access to the Flash from user space (without requiring a system call).
89     block library to enable this user space access.  The driver supports
111     Applications intending to get access to the CXL Flash from user
115     The block library can be thought of as a 'user' of services,
117     specifically for devices (LUNs) operating in user space access
131     device (LUN) via user space access need to use the services provided
134     the communication channel between a user and the kernel.  This file
139     driver. Upon successful open, the user receives a file descriptor
157     notification and access in the event of a non-user-initiated close(),
162     and fd2) that are provided back to the user:
174         - When a context is no longer needed, the user shall detach from
178           required by the user.
184     user space on a per-context basis. Additionally, the block size and
185     last logical block address (LBA) are returned to the user.
187     As mentioned previously, when operating in user space access mode,
192     The AFU is configured for direct access from user space by adding an
194     treated as a resource handle that is returned to the user. The user
200     of access and configuring the AFU for virtual access from user space
202     block address (LBA) are returned to the user.
204     As mentioned previously, when operating in user space access mode,
209     The AFU is configured for virtual access from user space by adding
211     is treated as a resource handle that is returned to the user. The
212     user is then able to use the handle to reference the LUN during I/O.
214     By default, the virtual LUN is created with a size of 0. The user
217     resize for the initial creation of the virtual LUN, the user has the
219     ioctl, such that when success is returned to the user, the
227     mode. Upon success, an updated last LBA is returned to the user
254     success, all "tokens" which had been provided to the user from the
261     support maintaining user space access to storage after a process
269     and playback required by a user in such a scenario. When a process
285     The user calls in when they want to validate that a LUN hasn't been
286     changed in response to a check condition. As the user is operating out
288     the kernel's knowledge. When encountered, the user's architected
297     of a specified user context. Any state associated with the user context
303     architected behavior for a user is to call into this ioctl to recover
304     their context. A user may also call into this ioctl at any time to
306     from this ioctl, the user is expected to gracefully clean up their
308     hold is not relinquished. The user may also optionally exit the process
316     exclusive user space access (superpipe). In case a LUN is visible