Project

General

Profile

Feature #68

LRTS support for setting up a message to send and transmitting a GET handle

Added by Phil Miller over 6 years ago. Updated about 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
03/01/2013
Due date:
% Done:

0%


Description

On platforms that use GET-based RDMA for large messages, there are various circumstances where it is useful to be able to set up a message for transmission, and get a handle that an eventual recipient can be told to retrieve. Use cases generally involved large messages. Interacting use cases include constrained receiver-side memory, and message delivery to migrated objects.


Related issues

Related to Charm++ - Feature #1234: Avoid sender-side copy for large contiguous messages. API for charm and converse layers Merged 06/22/2016
Blocks Charm++ - Feature #69: Get large messages sent via the ZC API to be received directly using a GET from the new home. (rather than a GET from the old home and forwarding the large message) New 03/01/2013

History

#1 Updated by Phil Miller over 6 years ago

  • Subject changed from LRTS support for setting up a message to send and transmitting a handle to LRTS support for setting up a message to send and transmitting a GET handle

#2 Updated by Phil Miller over 6 years ago

  • Target version set to 6.6.0

#3 Updated by Phil Miller almost 6 years ago

  • Target version changed from 6.6.0 to 6.7.0

Not on the release radar, and no implementation on the horizon within the time remaining.

#4 Updated by Nikhil Jain over 3 years ago

  • Target version changed from 6.7.0 to 6.8.0

#5 Updated by Phil Miller over 2 years ago

Looks like the code for #1234 essentially addresses this desire. Try it out in CharmLU, perhaps.

#6 Updated by Eric Bohm over 2 years ago

  • Status changed from New to In Progress
  • Assignee set to Vipul Harsh

Is this solved by #1234?

#7 Updated by Sam White about 2 years ago

  • Status changed from In Progress to Closed

I think this issue is covered by the combination of the separate sender-side and receiver-side issues.

Also available in: Atom PDF