Skip to content

feat(ccu): integrate internal collective backend - #76

Draft
Kur0x wants to merge 2 commits into
codex/ccu-stack-04-runtimefrom
codex/ccu-stack-05-backend
Draft

feat(ccu): integrate internal collective backend#76
Kur0x wants to merge 2 commits into
codex/ccu-stack-04-runtimefrom
codex/ccu-stack-05-backend

Conversation

@Kur0x

@Kur0x Kur0x commented Jul 28, 2026

Copy link
Copy Markdown
Member

Summary

  • add runtime session, executor, and collective planner ownership
  • integrate direct CCU as an internal collective backend
  • preserve communicator fallback when direct CCU is unavailable
  • add smoke infrastructure and backend/API boundary guards

Stack

5 of 9. Depends on codex/ccu-stack-04-runtime.

Validation

  • git diff --check
  • 75 focused backend, smoke-source, runner, and public-boundary tests passed; 3 skipped
  • compiled and ran tests/comm/unit/test_tilexr_source_guards.cpp
  • output: TileXR source guard checks passed

Scope

Host-only validation. Hardware smoke is not rerun in this PR.


auto *comm = static_cast<TileXR::TileXRComm *>(request.comm);
TileXR::TileXRCcuBackend *backend = comm->GetCcuBackendForCollectives();
if (backend == nullptr || !backend->Available()) {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In production this condition is always true for a forced CCU request: none of the normal TileXRComm initialization paths call InitCcuBackend; the only caller is EnableCcuBackendForTest. Consequently the newly public TILEXR_COLLECTIVE_BACKEND_CCU option always returns TILEXR_ERROR_NOT_INITIALIZED. Please initialize the backend in the normal communicator lifecycle or lazily before dispatch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants