Lines Matching full:ctl

2 CTL - CAM Target Layer Description
12 Configuring and Running CTL
21 CTL is a disk, processor and cdrom device emulation subsystem originally
26 (who acquired Copan's assets in 2010) and Spectra Logic in 2010, CTL is
28 that Spectra would work to get CTL into the FreeBSD tree.
52 Configuring and Running CTL:
55  - Add 'device ctl' to your kernel configuration file or load the module.
70  - You should now see the CTL disk LUN through camcontrol devlist:
76    This is visible through the CTL CAM SIM.  This allows using CTL without
81    target mode enabled, you should now also be able to see the CTL LUNs via
84    Note that all CTL LUNs are presented to all frontends.  There is no
166  - Added in the second HA mode (where CTL does the data transfers instead
167    of having data transfers done below CTL), and abstracted out the Copan
170  - Fixed the phantom device problem in the CTL CAM SIM and improved the
187  - Added descriptor sense support to CTL.  It can be enabled through the
209  - CTL initialization process has been revamped.  Instead of using an
224  - Use devstat(9) for CTL's statistics collection.  CTL uses a home-grown
230  - ZFS ARC backend for CTL.  Since ZFS copies all I/O into the ARC
233    optimal solution for backing targets served by CTL with ZFS would be to
237  - Switch CTL over to using CAM CCBs instead of its own union ctl_io.  This
240    will also require changes to the CAM CCB structure to support CTL.
245 CTL has the concept of pluggable frontend ports and backends.  All
249 ctl.c:
252 This is the core of CTL, where all of the command handlers and a lot of
257 Here is a roadmap of some of the primary functions in ctl.c.  Starting here
281 ctl.h:
290 These files define the basic CTL backend API.  The comments in the header
314 functions defined for supported opcodes.  It is included in ctl.c.
325 CTL-specific wrappers around the CAM sense building functions.
331 These files define the basic CTL frontend port API.  The comments in the
337 This is a CTL frontend port that is also a CAM SIM.  The idea is that this
338 frontend allows for using CTL without any target-capable hardware.  So any
339 LUNs you create in CTL are visible via this port.
350 This defines most of the core CTL I/O structures.  union ctl_io is
356 This defines all ioctls available through the CTL character device, and
362 Private data structres (e.g. CTL softc) and function prototypes.  This also
363 includes the SCSI vendor and product names used by CTL.
369 CTL wrappers around CAM sense printing functions.
383 CTL utility functions, primarily designed to be used from userland.  See
390 CAM target peripheral driver and CTL frontend port.  This is the path into
391 CTL for commands from target-capable hardware/SIMs.
400 for CTL.