Lines Matching full:user
24 CXL provides a mechanism by which user space applications can
27 user space application direct access to Flash storage.
33 special path for user space access, and performing error recovery. It
44 user space with a special block library. This mode further
59 directly in each user I/O, but at the minimum is involved in the
60 initial setup before the user application is allowed to send requests
68 | 512 * 64 KB User MMIO |
70 | User Accessible |
90 access to the Flash from user space (without requiring a system call).
93 block library to enable this user space access. The driver supports
115 Applications intending to get access to the CXL Flash from user
119 The block library can be thought of as a 'user' of services,
121 specifically for devices (LUNs) operating in user space access
135 device (LUN) via user space access need to use the services provided
138 the communication channel between a user and the kernel. This file
143 driver. Upon successful open, the user receives a file descriptor
161 notification and access in the event of a non-user-initiated close(),
166 and fd2) that are provided back to the user:
184 - When a context is no longer needed, the user shall detach from
194 + Following a successful detach of the last user of the context
207 user space on a per-context basis. Additionally, the block size and
208 last logical block address (LBA) are returned to the user.
210 As mentioned previously, when operating in user space access mode,
215 The AFU is configured for direct access from user space by adding an
217 treated as a resource handle that is returned to the user. The user
223 of access and configuring the AFU for virtual access from user space
225 block address (LBA) are returned to the user.
227 As mentioned previously, when operating in user space access mode,
232 The AFU is configured for virtual access from user space by adding
234 is treated as a resource handle that is returned to the user. The
235 user is then able to use the handle to reference the LUN during I/O.
237 By default, the virtual LUN is created with a size of 0. The user
240 resize for the initial creation of the virtual LUN, the user has the
242 ioctl, such that when success is returned to the user, the
248 provides the user with a hint that I/O can be retried in the event
255 mode. Upon success, an updated last LBA is returned to the user
265 In addition to returning a failure to user, cxlflash will also schedule
266 an asynchronous AFU reset. Should the user choose to retry the operation,
267 it is expected to succeed. If this ioctl fails with -EAGAIN, the user
288 success, all "tokens" which had been provided to the user from the
293 following the detach of the final user of the context.
299 support maintaining user space access to storage after a process
307 and playback required by a user in such a scenario. When a process
323 In addition to returning a failure to user, cxlflash will also schedule
324 an asynchronous AFU reset. Should the user choose to retry the operation,
325 it is expected to succeed. If this ioctl fails with -EAGAIN, the user
335 The user calls in when they want to validate that a LUN hasn't been
336 changed in response to a check condition. As the user is operating out
338 the kernel's knowledge. When encountered, the user's architected
347 of a specified user context. Any state associated with the user context
350 User contexts are put into an error condition when the device needs to
353 architected behavior for a user is to call into this ioctl to recover
354 their context. A user may also call into this ioctl at any time to
356 from this ioctl, the user is expected to gracefully clean up their
358 hold is not relinquished. The user may also optionally exit the process
371 exclusive user space access (superpipe). In case a LUN is visible
429 data transfer, the user supplies an adequately sized data buffer and must
433 transfer, the data buffer is not copied back to the user.