write a Legion scheduler
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2.4k
- Forks
- 270
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 39
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.
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 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.
Assessment
- Tech stack
- cpp
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100