8.1. Mapping by App Plans
Implementation plans for supporting independent mapping strategies for each app
- 8.1.1. Per-App-Context Mapping Policies
- 8.1.1.1. Overview
- 8.1.1.2. Goals
- 8.1.1.3. Attributes Required on
prte_app_context_t - 8.1.1.4. Changes to
prte_rmaps_options_t(src/mca/rmaps/rmaps_types.h) - 8.1.1.5. New Parsing Functions (
src/mca/rmaps/base/rmaps_base_frame.c) - 8.1.1.6. Changes to
prte_rmaps_base_map_job()(src/mca/rmaps/base/rmaps_base_map_job.c) - 8.1.1.7. Changes to rmaps Components
- 8.1.1.8. Changes to Ranking
- 8.1.1.9. Changes to Binding
- 8.1.1.10. Command-line / PMIx-spawn wiring
- 8.1.1.11. Migration Notes
- 8.1.1.12. Files Modified
- 8.1.1.13. Resolved Design Decisions
- 8.1.1.14. Framework Version Increment
- 8.1.1.15. Unit Tests
- 8.1.1.16.
make checkIntegration - 8.1.1.17. Open Questions
- 8.1.2. Per-App-Context Mapping: Implementation Plan
- 8.1.3. Per-App-Context Mapping: Implementation Tasks
- 8.1.3.1. Phase 1 — Data Model
- 8.1.3.2. Phase 2 — Parsing Functions
- 8.1.3.3. Phase 3 — Per-App Dispatch in
prte_rmaps_base_map_job() - 8.1.3.4. Phase 4 — Ranking with
app_idx - 8.1.3.5. Phase 5 — Component
app_idxGuards - 8.1.3.6. Phase 6 — Schizo / CLI Wiring
- 8.1.3.7. Phase 7 — Build System
- 8.1.3.8. Phase 8 — Unit Tests
- 8.1.3.9. Completion Checklist