uDAPL status

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!