Lines Matching +full:mode +full:- +full:capable
2 CTL - CAM Target Layer Description
27 available under a BSD-style license. The intent behind the agreement was
33 - Disk, processor and cdrom device emulation.
34 - Tagged queueing
35 - SCSI task attribute support (ordered, head of queue, simple tags)
36 - SCSI implicit command ordering support. (e.g. if a read follows a mode
37 select, the read will be blocked until the mode select completes.)
38 - Full task management support (abort, LUN reset, target reset, etc.)
39 - Support for multiple ports
40 - Support for multiple simultaneous initiators
41 - Support for multiple simultaneous backing stores
42 - Support for VMWare VAAI: COMPARE AND WRITE, XCOPY, WRITE SAME and
44 - Support for Microsoft ODX: POPULATE TOKEN/WRITE USING TOKEN, WRITE SAME
46 - Persistent reservation support
47 - Mode sense/select support
48 - Error injection support
49 - High Availability clustering support with ALUA
50 - All I/O handled in-kernel, no userland context switch overhead.
55 - Add 'device ctl' to your kernel configuration file or load the module.
57 - If you're running with a 8Gb or 4Gb Qlogic FC board, add
61 - Rebuild and install a new kernel.
63 - Reboot with the new kernel.
65 - To add a LUN with the RAM disk backend:
67 ctladm create -b ramdisk -s 10485760000000000000
68 ctladm port -o on
70 - You should now see the CTL disk LUN through camcontrol devlist:
74 <> at scbus6 target -1 lun -1 ()
80 If any target-capable HBAs are in the system (e.g. isp(4)), and have
81 target mode enabled, you should now also be able to see the CTL LUNs via
85 LUN masking, or separate, per-port configuration.
87 - Note that the ramdisk backend is a "fake" ramdisk. That is, it is
91 - To add a LUN with the block/file backend:
93 truncate -s +1T myfile
94 ctladm create -b block -o file=myfile
95 ctladm port -o on
97 - You can also see a list of LUNs and their backends like this:
114 - You can see the LUN type and backing store for block/file backend LUNs
117 # ctladm devlist -v
166 - Added in the second HA mode (where CTL does the data transfers instead
170 - Fixed the phantom device problem in the CTL CAM SIM and improved the
174 - Made the number of threads in the block backend configurable via sysctl,
176 -o num_threads=4 when creating a LUN with ctladm create.)
178 - Fixed some LUN selection issues in ctlstat(8) and allowed for selection
181 - General cleanup.
183 - This version intended for public release.
187 - Added descriptor sense support to CTL. It can be enabled through the
188 control mode page (10), but is disabled by default.
190 - Improved error injection support. The number of errors that can be
194 - The port infrastructure has been revamped. Individual ports and types
198 - The block backend can now send multiple I/Os to backing files. Multiple
202 - The block and ramdisk backends now support setting the LUN blocksize.
209 - CTL initialization process has been revamped. Instead of using an
210 ad-hoc method, it is now sequenced through SYSINIT() calls.
212 - A block/file backend has been added. This allows using arbitrary files
215 - The userland LUN configuration interface has been completely rewritten.
218 - The ctladm(8) command line interface has been revamped, and is now
224 - Use devstat(9) for CTL's statistics collection. CTL uses a home-grown
227 available in iostat to match the behavior of ctlstat -t and dump modes
228 are available to match the behavior of ctlstat -d/ctlstat -J.
230 - ZFS ARC backend for CTL. Since ZFS copies all I/O into the ARC
232 ZFS-backed zdev or file will involve an extra set of copies. The
237 - Switch CTL over to using CAM CCBs instead of its own union ctl_io. This
247 ramdisk-backed LUN present along side a file backed LUN.
250 -----
263 ctl_queue_sense() This is only used for non-packetized SCSI. i.e.
282 -----
288 -------------
294 -------------------
302 ---------------------
311 ---------------
317 -----------
323 -----------
325 CTL-specific wrappers around the CAM sense building functions.
329 --------------
335 ----------------------
338 frontend allows for using CTL without any target-capable hardware. So any
343 --------
345 This is a High Availability API and TCP-based interlink implementation.
348 --------
354 -----------
360 -------------
367 --------------
372 ---------------
376 you have a mode select followed by a write? You block the write until the
377 mode select is complete. That is defined in this table.
381 ----------
388 ----------
391 CTL for commands from target-capable hardware/SIMs.