1 / 7

uDAPL status

The uDAPL 2.0 specification draft is almost ready for ratification, with headers synchronized and compiled with OFA headers. iWARP extension headers need to be completed. A new document is available to assist users in transitioning to uDAPL 2.0, which is not backward source compatible. The spec features include Common Connection Model, HA extensions with load-balancing, IB and iWARP extension support, RDMA Write with Immediate & Atomic, iWARP Socket connection model, DAPL core extension support, and more. Over 30 errata have been closed.

jspring
Download Presentation

uDAPL status

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. uDAPL status Arkady Kanevsky Network Appliance

  2. DAT 2.0 spec status • Draft is basically ready for ratification • Headers compiled and synchronized with OFA headers (minor sync left) • iWARP extensions headers need to be completed • New document for users to help with application transition to uDAPL 2.0 since it is not backward source compatible

  3. uDAPL 2.0 spec features • Common Connection Model • HA extensions including load-balancing • IB and iWARP extension support • IB: RDMA Write with Immediate & Atomic • iWARP: Socket connection model • DAPL core extension support: event stream • FileDescriptor CNO and EVD extensions

  4. uDAPL 2.0 spec features • remaining iWARP and IB verbs extension support • send with invalidate • virtual address type for LMR and RMR create • RMR scope (single vs all connections) • RDMA Read to locally specified RMR • errors additions • Header changes for perf & info • data transfer completion event additions: operation type • LMR & RMR triplet formats aligned with OFA • LMR_handle for RMR_bind as well as LMR_context • thread, signal, blocking and exception handler safety function clarification • more than 30 errata closed • cr_reject private_data

  5. kernel features not exposed in uDAPL • Zero-based virtual addresses • FMR • LMR scope • Physical memory & Reserved LMR

  6. What about DAT 2.0 in OFA? • Questions to uDAPL maintainers: Arlin and James • When? • we can do placeholders now • For true implementation verbs are needed to be done first (IBTA 1.2 extension & iWARP) • Prioritize the feature list…

  7. THANK YOU!

More Related