[Feature] Support Immediate Data with Signal/Wait
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 557
- Forks
- 107
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 22
Description
The discussion originated from PR https://github.com/microsoft/mscclpp/pull/366
It may be useful to piggyback a small amount of immediate data (e.g., 4 bytes) with signal(), similar to imm_data in InfiniBand write requests. This could eliminate the need for a separate memory read when communicating small metadata alongside synchronization.
Potential implementation options include:
Sending the immediate data together with the signal.
Leveraging imm_data for IB connections.
This issue serves as a backlog item for future evaluation.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing PR #366 and the existing signal()/wait() entry points, then compare the two proposed approaches: carrying data with signal or using InfiniBand imm_data. This is a backlog item with no defined completion criteria, so clarify the API, supported connection types, and validation tests before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- distributed-systems, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100