What is SCSI RDMA PROTOCOL? What does SCSI RDMA PROTOCOL mean? SCSI RDMA PROTOCOL meaning

✪✪✪✪✪ http://www.theaudiopedia.com ✪✪✪✪✪

What is SCSI RDMA PROTOCOL? What does SCSI RDMA PROTOCOL mean? SCSI RDMA PROTOCOL meaning - SCSI RDMA PROTOCOL definition - SCSI RDMA PROTOCOL explanation.

Source: Wikipedia.org article, adapted under https://creativecommons.org/licenses/by-sa/3.0/ license.

SUBSCRIBE to our Google Earth flights channel - https://www.youtube.com/channel/UC6UuCPh7GrXznZi0Hz2YQnQ


In computing the SCSI RDMA Protocol (SRP) is a protocol that allows one computer to access SCSI devices attached to another computer via remote direct memory access (RDMA). The SRP protocol is also known as the SCSI Remote Protocol. The use of RDMA makes higher throughput and lower latency possible than what is possible through e.g. the TCP/IP communication protocol. RDMA is only possible with network adapters that support RDMA in hardware. Examples of such network adapters are InfiniBand HCAs and 10 GbE network adapters with iWARP support. While the SRP protocol has been designed to use RDMA networks efficiently, it is also possible to implement the SRP protocol over networks that do not support RDMA.

SRP was published as an ANSI standard (ANSI INCITS 365-2002) in 2002 and renewed in 2007.

As with the ISCSI Extensions for RDMA (iSER) communication protocol, there is the notion of a target (a system that stores the data) and an initiator (a client accessing the target) with the target performing the actual data movement. In other words, when a user writes to a target, the target actually executes a read from the initiator and when a user issues a read, the target executes a write to the initiator.

While the SRP protocol is easier to implement than the iSER protocol, iSER offers more management functionality, e.g. the target discovery infrastructure enabled by the iSCSI protocol.

In order to use the SRP protocol, an SRP initiator implementation, an SRP target implementation and networking hardware supported by the initiator and target are needed. The following software SRP initiator implementations exist:

Linux SRP initiator, available since November 2005 (kernel version 2.6.15).
Windows SRP initiator, available through the winOFED InfiniBand stack.
VMWare SRP initiator, available since January 2008 through Mellanox' OFED Drivers for VMware Infrastructure 3 and vSphere 4.
Solaris 10 SRP initiator, available through Sun's download page.
Solaris 11 and OpenSolaris SRP initiator, integrated as a component of project COMSTAR.
The IBM POWER virtual SCSI client driver for Linux (ibmvscsi), available since January 2008 (kernel version 2.6.24). Virtual SCSI allows client logical partitions to access I/O devices (disk, CD, and tape) that are owned by another logical partition.
The following SRP target implementations exist:

The SCST SRP target implementation. This is a mature SRP target implementation available since 2008 via both SCST and OFED.
Linux LIO SRP target, available since January 2012 (kernel version 3.3), based on the SCST SRP target.
The IBM POWER virtual SCSI target driver (ibmvstgt), available since January 2008 (kernel version 2.6.24).
DataDirect Network's (DDN) disk subsystems such as the S2A9900 and SFA10000, which use the SRP target implementation in the disk subsystem's controllers to present LUNs to servers (the servers act as SRP initiators).
IBM's FlashSystem.
The Solaris COMSTAR target, available since early 2009 in OpenSolaris and Solaris 11.
Bandwidth and latency of storage targets supporting the SRP or the iSER protocol should be similar. On Linux, there are two SRP and two iSER storage target implementations available that run inside the kernel (SCST and LIO) and an iSER storage target implementation that runs in user space (STGT). Measurements have shown that the SCST SRP target has a lower latency and a higher bandwidth than the STGT iSER target. This is probably because the RDMA communication overhead is lower for a component implemented in the Linux kernel than for a user space Linux process, and not because of protocol differences.