Lines Matching refs:kernel

24 TCM is another name for LIO, an in-kernel iSCSI target (server).
25 Existing TCM targets run in the kernel.  TCMU (TCM in Userspace)
29 The existing kernel provides modules for different SCSI transport
33 built-in modules are implemented entirely as kernel code.
38 SCSI commands ("fabrics"), the Linux kernel target, LIO, also modularizes
43 these are implemented entirely as kernel code.
46 use case that other non-kernel target solutions, such as tgt, are able
57 difficult, because LIO is entirely kernel code. Instead of undertaking
59 kernel, another approach is to create a userspace pass-through
83 - Allow future flexibility in user & kernel implementations
92 between kernel and userspace. Within this region is: a control area
115 command ring, and head and tail pointers to be used by the kernel and
125 cmd_head - Modified by the kernel to indicate when a command has been
132 Commands are placed on the ring by the kernel incrementing
136 signals the kernel via a 4-byte write(). When cmd_head equals
143 flags fields for setting by the kernel (kflags) and userspace
163 kernel via the UIO method, a 4-byte write to the file descriptor.
166 it's a no-op. (The kernel inserts PAD entries to ensure each CMD entry
193 kernel target's configfs tree. Assuming the usual mount point, it is
196 /sys/kernel/config/target/core/user_<hba_num>/<device_name>
238   the kernel will abort pending tasks.
242 - The kernel will abort pending tasks after a timeout period.
247   but should not be able to access kernel memory outside its shared
260    possibly sense_buffer), updating cmd_tail, and notifying the kernel
342       /* Tell the kernel we didn't handle unknown opcodes */
355   /* Notify the kernel that work has been finished */