JACCL mesh versus ring topology selection and per-pair device counts
Parent: Mac local LLMs: Clusters, RDMA, exo and ds4 · Published reference · snapshot 2026-10-05
↓ Facts as markdownall context files
Already covered: jaccl-ring-all-reduce-wire-partitioning-n-wires.md (selection order in init, MLX_JACCL_RING, is_valid_ring per-pair device count, mesh n_wires as minimum over pairs, MESH_MAX_PEERS 8, RING_MAX_CONNS 4) and distributed-inference-across-macs.md.
These notes link each claim to its source. A source may be a research report hosted on this site rather than the primary document. A published reference means the content is available; it does not certify independent review or accuracy.Read the editorial policy and follow the sources before relying on a claim.
Facts
- Already covered: jaccl-ring-all-reduce-wire-partitioning-n-wires.md (selection order in init, MLX_JACCL_RING, is_valid_ring per-pair device count, mesh n_wires as minimum over pairs, MESH_MAX_PEERS 8, RING_MAX_CONNS 4) and distributed-inference-across-macs.md. [source]
Corrections and disagreements
- CONTRADICTS (docs vs source, not stated in existing files): the MLX distributed docs say JACCL supports only fully connected topologies, while jaccl.cpp init falls back to a valid ring. [source]
Children
- No children recorded.