u DAPL status Arkady Kanevsky Network Appliance http

u. DAPL status Arkady Kanevsky Network Appliance http: //openfabrics. org/

DAT 2. 0 spec status Ø Draft is basically ready for ratification ØHeaders compiled and synchronized with OFA headers (minor sync left) Øi. WARP extensions headers need to be completed ØNew document for users to help with application transition to u. DAPL 2. 0 since it is not backward source compatible http: //openfabrics. org/ 2

u. DAPL 2. 0 spec features Ø Common Connection Model Ø HA extensions including load-balancing Ø IB and i. WARP extension support ØIB: RDMA Write with Immediate & Atomic Øi. WARP: Socket connection model ØDAPL core extension support: event stream Ø File. Descriptor CNO and EVD extensions http: //openfabrics. org/ 3

u. DAPL 2. 0 spec features Ø remaining i. WARP 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 http: //openfabrics. org/ 4

kernel features not exposed in u. DAPL Ø Zero-based virtual addresses Ø FMR Ø LMR scope Ø Physical memory & Reserved LMR http: //openfabrics. org/ 5

What about DAT 2. 0 in OFA? Ø Questions to u. DAPL maintainers: Arlin and James Ø When? Øwe can do placeholders now ØFor true implementation verbs are needed to be done first (IBTA 1. 2 extension & i. WARP) Ø Prioritize the feature list… http: //openfabrics. org/ 6

THANK YOU! http: //openfabrics. org/