Remote direct memory access: Difference between revisions

Revision as of 15:12, 26 December 2006

Revision as of 10:07, 9 January 2007

Line 9:

RDMA’s acceptance is also limited by the need to install a different networking infrastructure. New standards enable [[Ethernet]] RDMA implementation at the physical layer and [[Transmission Control Protocol|TCP]]/[[Internet Protocol|IP]] as the transport, combining the performance and latency advantages of RDMA with a low-cost, standards-based solution. The RDMA Consortium and the DAT Collaborative<ref>[http://www.datcollaborative.org/ DAT Collaborative website.]</ref> have played key roles in the development of RDMA protocols and [[Application programming interface|APIs]] for consideration by standards groups such as the [[Internet Engineering Task Force]] and the Interconnect Software Consortium.<ref>[http://www.opengroup.org/icsc/ The Interconnect Software Consortium website.]</ref> Software vendors such as [[Oracle Corporation]] support these APIs in their latest products, and network adapters that implement RDMA over Ethernet are being developed.

Common RDMA implementations include the [[Virtual Interface Architecture]], [[InfiniBand]], and [[iWARP]].

The most common RDMA implementation is over [[InfiniBand]], which is technologically superior to most alternatives but faces an uncertain commercial future.

==Notes==