Lines Matching refs:LUN
34 operation at the device (LUN) level:
36 - Any flash device (LUN) can be configured to be accessed as a
39 - Any flash device (LUN) can be configured to be accessed from
42 either raw access to the entire LUN (referred to as direct
43 or physical LUN access) or access to a kernel/AFU-mediated
44 partition of the LUN (referred to as virtual LUN access). The
81 scsi block devices (/dev/sdb, /dev/sdc etc.) for each unique LUN
100 and the entire space for the LUN is available to the application.
127 CXL Flash Driver LUN IOCTLs
131 device (LUN) via user space access need to use the services provided
136 with the scsi disk device (/dev/sdb) that was created during LUN
201 This ioctl is responsible for transitioning the LUN to direct
209 requests to use the LUN in a different mode are denied.
214 is then able to use the handle to reference the LUN during I/O.
218 This ioctl is responsible for transitioning the LUN to virtual mode
226 requests to use the LUN in a different mode are denied.
231 user is then able to use the handle to reference the LUN during I/O.
233 By default, the virtual LUN is created with a size of 0. The user
235 the virtual LUN to a desired size. To avoid having to perform this
236 resize for the initial creation of the virtual LUN, the user has the
242 When a LUN is accessible from more than one port, this ioctl will
245 of an I/O error as the LUN can be reached over multiple paths.
250 LUN and will fail if invoked upon a LUN that is not in virtual
252 indicating the new size of the virtual LUN associated with the
256 driver and the AFU. An allocation table is kept for each LUN that is
257 operating in the virtual mode and used to program a LUN translation
269 reference to either a physical or virtual LUN. This can be
275 As part of the release process for virtual LUNs, the virtual LUN
277 associated with the virtual LUN reference.
328 where the changes affect the application (such as a LUN resize), the
331 The user calls in when they want to validate that a LUN hasn't been
337 verifying a LUN change (ie: size different) with sense data is
365 This ioctl is used to switch a LUN from a mode where it is available
367 exclusive user space access (superpipe). In case a LUN is visible
369 identify each LUN by its World Wide Node Name (WWNN).
389 devices that lack an external LUN management interface. It is only
390 valid when used with AFUs that support the LUN provision capability.
393 the target port to host the LUN and a desired size in 4K blocks. Upon
394 success, the LUN ID and WWID of the created LUN will be returned and
395 the SCSI bus can be scanned to detect the change in LUN topology. Note
397 to a space issue, the target port can be queried for its current LUN
400 To remove a LUN, the device must first be disassociated from the Linux
401 SCSI subsystem. The LUN deletion can then be initiated by specifying a
402 target port and LUN ID. Upon success, the LUN geometry associated with
406 To query the LUN geometry of a port, the target port is specified and