write a Legion scheduler
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- distributed-systems
Research direction
Start by reading stdexec's scheduler model and the Legion and Thrust APIs mentioned in the issue. Define the scope for a Legion scheduler and async Thrust algorithms that accept schedulers, then validate the proposed sync_wait(thrust_algorithm(legion_scheduler, arguments...)) usage as the completion target.
Written by the indexing model from the issue text.
Description
I think there is a good story we can tell about how stdexec can add value to Legion. Consider:
- We intend to write a Legion scheduler for stdexec
- We intent to write async versions of the Thrust algorithms that take schedulers
Putting 2 and 2 together, we can make it utterly trivial for anybody currently using Thrust (lots of developers) to target the Legion runtime:
// Execute a Thrust algorithm on Legion:
auto [results...] = sync_wait(thrust_algorithm(legion_scheduler, arguments...)).value();
That's obviously just scratching the surface.
- Dominant language
- C++
- Stars
- 2.4k
- Forks
- 270
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 37
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.
More from NVIDIA/stdexec
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 66/100
-
Difficulty 3/5 1-2 days Newbie friendliness 74/100
Similar issues
-
ai_reviewed
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
ydb-platform/ydb#53869 · 3 comments ·
-
bug cert blocker needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
project-chip/connectedhomeip#74373 ·
-
upstream update
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
conan-io/conan-center-index#31035 ·
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 85/100
vllm-project/vllm-ascend#17329 ·