| LIO Target | |
| Author: | Nicholas Bellinger Jerome Martin |
| Developer: | Datera, Inc. |
| Programming Language: | C, Python |
| Operating System: | Linux |
| Genre: | Block storage |
| License: | GNU General Public License |
In computing, Linux-IO (LIO) Target is an open-source implementation of the SCSI target that has become the standard one included in the Linux kernel.[1] Internally, LIO does not initiate sessions, but instead provides one or more Logical Unit Numbers (LUNs), waits for SCSI commands from a SCSI initiator, and performs required input/output data transfers. LIO supports common storage fabrics, including FCoE, Fibre Channel, IEEE 1394, iSCSI, iSCSI Extensions for RDMA (iSER), SCSI RDMA Protocol (SRP) and USB. It is included in some Linux distributions; native support for LIO in QEMU/KVM, libvirt, and OpenStack makes LIO also a storage option for cloud deployments.[2] [3]
LIO is maintained by Datera, Inc., a Silicon Valley provider of storage systems and software. On January 15, 2011, LIO SCSI target engine was merged into the Linux kernel mainline, in kernel version 2.6.38,[4] [5] which was released on March 14, 2011. Additional fabric modules have been merged into subsequent Linux releases.
A competing generic SCSI target module for Linux is SCST.[6] For the narrower purpose providing a Linux iSCSI target, the older IET ("iSCSI Enterprise Target") and STGT ("SCSI Target FrameWork") modules also enjoy industry support.[7] [8]
The SCSI standard provides an extensible semantic abstraction for computer data storage devices, and as such has become a "lingua franca" for data storage systems. The SCSI T10 standards[9] define the commands[10] and protocols of the SCSI command processor (sent in SCSI CDBs), and the electrical and optical interfaces for various implementations.
A SCSI initiator is an endpoint that initiates a SCSI session. A SCSI target is the endpoint that waits for initiator commands and executes the required I/O data transfers. The SCSI target usually exports one or more LUNs for initiators to operate on.
The LIO Linux SCSI Target implements a generic SCSI target that provides remote access to most data storage device types over all prevalent storage fabrics and protocols. LIO neither directly accesses data nor does it directly communicate with applications. LIO provides a highly efficient, fabric-independent and fabric-transparent abstraction for the semantics of numerous data storage device types.
LIO implements a modular and extensible architecture around a versatile and highly efficient, parallelized SCSI command processing engine. The SCSI target engine implements the semantics of a SCSI target.[11]
The LIO SCSI target engine is independent of specific fabric modules or backstore types. Thus, LIO supports mixing and matching any number of fabrics and backstores at the same time. The LIO SCSI target engine implements a comprehensive SPC-3/SPC-4[12] feature set with support for high-end features, including SCSI-3/SCSI-4 Persistent Reservations (PRs), SCSI-4 Asymmetric Logical Unit Assignment (ALUA), VMware vSphere APIs for Array Integration (VAAI),[13] T10 DIF, etc.
LIO is configurable via a configfs-based[14] kernel API, and can be managed via a command-line interface and API (targetcli).
The concept of a SCSI target isn't narrowly restricted to physical devices on a SCSI bus, but instead provides a generalized model for all receivers on a logical SCSI fabric. This includes SCSI sessions across interconnects with no physical SCSI bus at all. Conceptually, the SCSI target provides a generic block storage service or server in this scenario.
Backstores provide the SCSI target with generalized access to data storage devices by importing them via corresponding device drivers. Backstores don't need to be physical SCSI devices.
The most important backstore media types are:
As a result, LIO provides a generalized model to export block storage.
Fabric modules implement the frontend of the SCSI target by encapsulating and abstracting the properties of the various supported interconnect. The following fabric modules are available.
The Fibre Channel over Ethernet (FCoE) fabric module allows the transport of Fibre Channel protocol (FCP) traffic across lossless Ethernet networks. The specification, supported by a large number of network and storage vendors, is part of the Technical Committee T11 FC-BB-5 standard.[15]
LIO supports all standard Ethernet NICs.
The FCoE fabric module was contributed by Cisco and Intel, and released with Linux 3.0 on July 21, 2011.[16]
Fibre Channel is a high-speed network technology primarily used for storage networking. It is standardized in the Technical Committee T11[17] of the InterNational Committee for Information Technology Standards (INCITS).
The QLogic Fibre Channel fabric module supports 4- and 8-gigabit speeds with the following HBAs:
The Fibre Channel fabric module[18] and low-level driver[19] (LLD) were released with Linux 3.5 on July 21, 2012.[20]
With Linux 3.9, the following QLogic HBAs and CNAs are also supported:
This makes LIO the first open source target to support 16-gigabit Fibre Channel.
The FireWire SBP-2 fabric module enables Linux to export local storage devices via IEEE 1394, so that other systems can mount them as an ordinary IEEE 1394 storage device.
IEEE 1394 is a serial-bus interface standard for high-speed communications and isochronous real-time data transfer. It was developed by Apple as "FireWire" in the late 1980s and early 1990s, and Macintosh computers have supported "FireWire target disk mode" since 1999.[21]
The FireWire SBP-2 fabric module was released with Linux 3.5 on July 21, 2012.[20] [22]
The Internet Small Computer System Interface (iSCSI) fabric module allows the transport of SCSI traffic across standard IP networks.
By carrying SCSI sessions across IP networks, iSCSI is used to facilitate data transfers over intranets and to manage storage over long distances. iSCSI can be used to transmit data over local area networks (LANs), wide area networks (WANs), or the Internet, and can enable location-independent and location-transparent data storage and retrieval.
The LIO iSCSI fabric module also implements a number of advanced iSCSI features that increase performance and resiliency, such as Multiple Connections per Session (MC/S) and Error Recovery Levels 0-2 (ERL=0,1,2).
LIO supports all standard Ethernet NICs.
The iSCSI fabric module was released with Linux 3.1 on October 24, 2011.[23]
Networks supporting remote direct memory access (RDMA) can use the iSCSI Extensions for RDMA (iSER) fabric module to transport iSCSI traffic.iSER permits data to be transferred directly into and out of remote SCSI computer memory buffers without intermediate data copies (direct data placement or DDP) by using RDMA. RDMA is supported on InfiniBand networks, on Ethernet with data center bridging (DCB) networks via RDMA over Converged Ethernet (RoCE), and on standard Ethernet networks with iWARP enhanced TCP offload engine controllers.
The iSER fabric module was developed together by Datera and Mellanox Technologies, and first released with Linux 3.10 on June 30, 2013.[24]
The SCSI RDMA Protocol (SRP) fabric module allows the transport of SCSI traffic across RDMA (see above) networks. As of 2013, SRP was more widely used than iSER, although it is more limited, as SCSI is only a peer-to-peer protocol, whereas iSCSI is fully routable.The SRP fabric module supports the following Mellanox host channel adapters (HCAs):
The SRP fabric module was released with Linux 3.3 on March 18, 2012.[25]
In 2012, c't magazine measured almost 5000 MB/s throughput with LIO SRP Target over one Mellanox ConnectX-3 port in 56 Gbit/s FDR mode on a Sandy Bridge PCI Express 3.0 system with four Fusion-IO ioDrive PCI Express flash memory cards.
The USB Gadget fabric module enables Linux to export local storage devices via the Universal Serial Bus (USB), so that other systems can mount them as an ordinary storage device.
USB was designed in the mid-1990s to standardize the connection of computer peripherals, and has also become common for data storage devices.
The USB Gadget fabric module was released with Linux 3.5 on July 21, 2012.[26]
targetcli is a user space single-node management command line interface (CLI) for LIO.[27] It supports all fabric modules and is based on a modular, extensible architecture, with plug-in modules for additional fabric modules or functionality.
targetcli provides a CLI that uses an underlying generic target library through a well-defined API. Thus the CLI can easily be replaced or complemented by a UI with other metaphors, such as a GUI.
targetcli is implemented in Python and consists of three main modules:
Detailed instructions on how to set up LIO targets can be found on the LIO wiki.[27]
targetcli and LIO are included in most Linux distributions per default. Here is an overview over the most popular ones, together with the initial inclusion dates:
| Distribution | Version | Release | Archive | Installation | Source git | Documentation | |
|---|---|---|---|---|---|---|---|
| Alpine Linux | 2.5 | 2011-11-07 | Alpine Linux mirror | apk add targetcli-fb | targetcli-fb.git | How-to | |
| CentOS | 6.2 | 2011-12-20 | CentOS mirror | su -c 'yum install fcoe-target-utils' | targetcli-fb.git | Tech Notes | |
| Debian | 7.0 ("wheezy") | 2013-05-04 | Debian pool | su -c 'apt-get install targetcli' | targetcli.git | LIO Wiki | |
| Fedora | 16 | 2011-11-08 | Fedora Rawhide | su -c 'yum install targetcli' | targetcli-fb.git | Target Wiki | |
| openSUSE | 12.1 | 2011-11-08 | Requires manual installation from Datera targetcli.git repos. | ||||
| RHEL | 6.2 | 2011-11-16 | Fedora Rawhide | su -c 'yum install fcoe-target-utils' | targetcli-fb.git | Tech Notes | |
| Scientific Linux | 6.2 | 2012-02-16 | SL Mirror | su -c 'yum install fcoe-target-utils' | targetcli-fb.git | Tech Notes | |
| SLES | 11 SP3 MR | 2013-12 | - | su -c 'zypper in targetcli' | targetcli.git | LIO Wiki | |
| Ubuntu | 12.04 LTS (precise) | 2012-04-26 | Ubuntu universe | sudo apt-get install targetcli | targetcli.git | LIO Wiki | |
| Release | Details | 2011 | 2012 | 2013 | 2014 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| width=1% | 1 | width=1% | 2 | width=1% | 3 | width=1% | 4 | width=1% | 5 | width=1% | 6 | width=1% | 7 | width=1% | 8 | width=1% | 9 | width=1% | 10 | width=1% | 11 | width=1% | 12 | width=1% | 1 | width=1% | 2 | width=1% | 3 | width=1% | 4 | width=1% | 5 | width=1% | 6 | width=1% | 7 | width=1% | 8 | width=1% | 9 | width=1% | 10 | width=1% | 11 | width=1% | 12 | width=1% | 1 | width=1% | 2 | width=1% | 3 | width=1% | 4 | width=1% | 5 | width=1% | 6 | width=1% | 7 | width=1% | 8 | width=1% | 9 | width=1% | 10 | width=1% | 11 | width=1% | 12 | width=1% | 1 | width=1% | 2 | width=1% | 3 | width=1% | 4 | width=1% | 5 | width=1% | 6 | width=1% | 7 | width=1% | 8 | width=1% | 9 | width=1% | 10 | width=1% | 11 | width=1% | 12 |
| 4.x< | -- 4.x Version --> | Version< | -- Leading blanks | --> | 4.1< | -- 4.x Trailing blanks --> | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Feature | Target Core | Loopback | FCoE | iSCSI | Perf | SRP | CM WQ | FC USB 1393 | vHost | Perf | Misc | 16 GFC | iSER | Misc | VAAI | Misc | DIF Ref's NPIV | iSER DIF | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Linux | 2.6.38 | 2.6.39 | 3.0 | 3.1 | 3.2 | 3.3 | 3.4 | 3.5 | 3.6 | 3.7 | 3.8 | 3.9 | 3.10 | 3.11 | 3.12 | 3.13 | 3.14 | 3.15 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||