Project

General

Profile

Feature #1116

AMPI broadcasts should be [nokeep]

Added by Sam White almost 3 years ago. Updated 3 months ago.

Status:
Merged
Priority:
Normal
Assignee:
Category:
AMPI
Target version:
Start date:
08/04/2016
Due date:
% Done:

0%


Description

AMPI_Bcast currently calls ampi::generic with an AmpiMsg. For broadcasts, we should invoke a version of ampi::generic that is tagged [nokeep] so the runtime can avoid making multiple copies of the message on the receiver side. Then we need to distinguish between 'expected' bcasts and 'unexpected' bcasts in AMPI: if a bcast is expected (already blocked on), then we can serialize the message data directly into the user's recvbuf. If it is not expected, then we copy the message and put it in our unexpected message queue to be processed whenever the receiver gets to the bcast.

This is similar to what I've done for (i)(all){reduce,gather(v)} here: https://charm.cs.illinois.edu/gerrit/#/c/1276/


Subtasks

Feature #1158: AMPI scatter(v) performance is poorNewSam White

History

#1 Updated by Sam White over 2 years ago

  • Status changed from New to In Progress

#2 Updated by Sam White over 2 years ago

  • Status changed from In Progress to Implemented

#3 Updated by Sam White over 2 years ago

  • Status changed from Implemented to In Progress

#4 Updated by Sam White over 2 years ago

  • Target version changed from 6.8.0 to 6.8.1

#5 Updated by Sam White over 1 year ago

  • Target version changed from 6.8.1 to 6.9.0

#6 Updated by Sam White about 1 year ago

  • Target version deleted (6.9.0)

#7 Updated by Sam White 6 months ago

  • Target version set to 6.9.1
  • Status changed from In Progress to Implemented

#8 Updated by Sam White 3 months ago

  • Status changed from Implemented to Merged

Also available in: Atom PDF