Project

General

Profile

Feature #1667

Direct User level API for nocopy operations on sender-side and receiver-side

Added by Nitin Bhat 27 days ago. Updated 6 days ago.

Status:
In Progress
Priority:
Normal
Assignee:
Category:
Machine Layers
Target version:
Start date:
08/29/2017
Due date:
% Done:

50%


Description

Since the receiver side API (https://charm.cs.illinois.edu/redmine/issues/1236) has restrictions which demand the user to name a generated entry method in a specific manner in order to overload the generated method, it will be a worthwhile effort to have an alternative API which is more direct as compared to entry method overloading and gives user the control to perform GET/PUT calls directly.

History

#1 Updated by Nitin Bhat 27 days ago

  • Tracker changed from Bug to Feature

#2 Updated by Nitin Bhat 27 days ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 50

#3 Updated by Sam White 27 days ago

  • Target version set to 6.9.0

We may want to avoid calling this "direct" since there is already something else called CmiDirect. I think in general the recv-side stuff is the completion of the Zero Copy API, but the fact that we will eventually have 2 APIs for the recv-side stuff will make it a bit confusing (I think of this API as the lower-level one, and the RdmaPost one as the higher-level abstraction).

#4 Updated by Phil Miller 27 days ago

  • Tags changed from #rdma to #rdma, ampi, #api, #machine-layers

#5 Updated by Phil Miller 27 days ago

If the generic layer gets done, possibly even with a hacky implementation that only really provides one of GET or PUT and uses that for the other, then we can implement the other layers piecemeal after the basic thing is integrated.

#6 Updated by Phil Miller 27 days ago

And similarly, that one-of-GET-or-PUT design can get us up and running on the other layers quickly, though, with an extra round trip, and then be optimized later.

Also available in: Atom PDF