Project

General

Profile

Feature #1366

AMPI thread should not be awoken unless progress can be made

Added by Sam White over 2 years ago. Updated over 2 years ago.

Status:
Merged
Priority:
Normal
Assignee:
Category:
AMPI
Target version:
Start date:
01/19/2017
Due date:
% Done:

0%


Description

AMPI's multiple completion routines currently block on any recv, while they could sleep until all or a specific request is matched.

History

#1 Updated by Sam White over 2 years ago

  • Target version changed from 6.8.0 to 6.8.1

#2 Updated by Sam White over 2 years ago

Support in AMPI_Wait* routines: https://charm.cs.illinois.edu/gerrit/#/c/2152/

Similar changes can be made in blocking recv and probe routines.

#3 Updated by Sam White over 2 years ago

  • Target version changed from 6.8.1 to 6.8.0
  • Status changed from New to In Progress

#4 Updated by Sam White over 2 years ago

  • Status changed from In Progress to Implemented

#5 Updated by Sam White over 2 years ago

  • Status changed from Implemented to Merged
  • translation missing: en.field_closed_date set to 2017-01-24 14:02:52.806240

I will follow up with the similar changes for recv and probe. They each have their own complications.

Recv: https://charm.cs.illinois.edu/gerrit/#/c/2155/

Probe would require pretty invasive changes. Perhaps we will wait until we have an application that is sensitive to this. Oftentimes a probe is used for any src/tag, so the first message that arrives will really be the right one anyways...

Also available in: Atom PDF