Bug #1519
Entry methods with no parameters ignore priority from CkEntryOptions
100%
Description
We've fixed zero-argument entry methods to accept CkEntryOptions at the call site, and to respect group construction dependences, so their semantics are at least strictly correct. We're just missing priority/queueing stategy now, which is part of the performance semantics, but not the program correctness.
It's clear why it's implemented this way - the code on both send and receive sides would have to be duplicated to choose between working with a zero-payload system message and a dynamically allocated message with room for a priority or whatever else the options might dictate. Nevertheless, it's a somewhat glaring and surprising inconsistency that some entry methods can be passed options, and others can't.
Related issues
History
#1 Updated by Phil Miller about 1 year ago
- Copied from Bug #987: Entry methods with no parameters can't be called with CkEntryOptions, can't take group construction dependence. added
#2 Updated by Nitin Bhat 6 months ago
- Status changed from New to Implemented
Fix: https://charm.cs.illinois.edu/gerrit/#/c/3265/
Along with setting priority, I also set the queuing type that the user can pass using CkEntryOptions.
#3 Updated by Nitin Bhat 3 months ago
- Status changed from Implemented to Merged