User Direct Access Programming Library: Difference between revisions
Appearance
Content deleted Content added
Ksacilotto (talk | contribs) Fix acronym for Virtual_Interface_Architecture. |
Peter Flass (talk | contribs) wow, someone was acronym-crazy! |
||
Line 1: | Line 1: | ||
{{Refimprove|date=June 2009}} |
{{Refimprove|date=June 2009}} |
||
A '''user direct access programming library''' (or uDAPL) defines a single set of user APIs for all [[Remote direct memory access |
A '''user direct access programming library''' (or uDAPL) defines a single set of user [[application program interface]]s (APIs) for all [[Remote direct memory access]] (RDMA)-capable transports. The uDAPL mission is to define a transport-independent and platform-standard set of APIs that exploit RDMA capabilities, such as those present in [[InfiniBand]], [[Virtual Interface Architecture]] (VIA), and ROI WG of [[Internet Engineering Task Force]] (IETF). |
||
==External links== |
==External links== |
Revision as of 23:58, 29 August 2016
This article needs additional citations for verification. (June 2009) |
A user direct access programming library (or uDAPL) defines a single set of user application program interfaces (APIs) for all Remote direct memory access (RDMA)-capable transports. The uDAPL mission is to define a transport-independent and platform-standard set of APIs that exploit RDMA capabilities, such as those present in InfiniBand, Virtual Interface Architecture (VIA), and ROI WG of Internet Engineering Task Force (IETF).
External links