Repository navigation
docs: hybrid scheduling, OpenMP-style teams with scoped stealing (design study, #22) - #23
Merged
Merged
Conversation
…ign study, #22) Theory only. Recommends one runtime, team first: tasks stolen only inside the creating token's domain, child stealing, a waiter runs descendants only, tasks carry no team authority, plain barriers run nothing (draining barrier opt-in), nested teams from idle domain workers or refusal, prepared graphs with rank priority, reproducible reductions over fixed chunks. Evaluates the two-pool option (engine owns a threadteam pool and a Rayon pool) item by item, with a comparison table, the deciding measurements, invariants, TLA+ properties and a staged introduction. Citations checked against primary sources; unverified ones are listed. Refs #22. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Design study for #22. Theory only, nothing implemented. It adds one file against
develop:docs/design/hybrid-scheduling.md.Maintainer direction (2026-10-30): 「threadteamを独自スレッドで拡張していくとしよう.OpenMPの機能をメインにするが,Rayonの柔軟性も取り込めないか?理論的に検討させよう」. Addendum: 「threadteamはOpenMP的にして,work stealingはRayonにますという手もあるね.例えば,tenferroのCPUEngineが両方のプールを持ってもいいわけだし.」
Recommendation
One runtime, team first, with scoped stealing.
join,scopeand prepared graphs are stolen only inside the creating token's domain. Pool scope is opt-in, as with OpenMP 6.0'sthreadset.isolate). Tasks carry no team authority, by type (TaskExec). A plain barrier runs nothing; a draining barrier is opt-in.taskgraph-like) with priority by remaining critical path.The two-pool option (an engine owns a threadteam pool and a Rayon pool) is evaluated item by item:
spin_polls;P/mloss of serial inner kernels;Parallelism::Pool;KMP_COMPOSABILITY,libirmlIPC,MKL_THREADING_LAYER).It is kept as the baseline every native stage has to beat. The note ends with a comparison table and six deciding measurements.
Coverage
Sources
KMP_COMPOSABILITY,libirmland--ipccome from the SciPy 2018 paper. oneTBB has nosrc/irml. NoOMP_*variable controls deterministic reductions. Kokkos tasking was removed in 5.0.Docs only. Base
develop. The monitor merges.🤖 Generated with Claude Code