You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: skills/mlx-distributed/references/multi-process.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,7 @@ JACCL (Joint Accelerator Communication Library) uses RDMA over Thunderbolt 5 for
25
25
- RDMA explicitly enabled in Recovery Mode (`csrutil`)
26
26
- Physical Thunderbolt 5 cable between nodes
27
27
28
-
> **Note:**MLX-C does not expose a backend selection parameter. You cannot force one backend over the other. If JACCL hardware is present, it will be preferred.
28
+
> **Note:**You can select a specific backend using the `backend` parameter (e.g., `MLXDistributed.\`init\`(backend: .jaccl)`). Use `.any` (the default) to let MLX choose automatically.
-`strict`: If `true`, returns `nil` on initialization failure instead of falling back to a singleton group. Default is `false`.
119
+
-`backend`: The backend to use. Default is `.any`, which lets MLX choose automatically.
110
120
111
121
**Returns:** The `DistributedGroup` for this process, or `nil` if `strict` is `true` and initialization failed.
112
122
113
-
When `strict` is `false` (default), returns a singleton group (rank 0, size 1) if no distributed backend can be initialized. MLX-C does not expose a backend selection parameter — it tries JACCL first, then ring.
123
+
When `strict` is `false` (default), returns a singleton group (rank 0, size 1) if no distributed backend can be initialized.
114
124
115
125
```swift
116
126
// Non-strict: always returns a group (size-1 fallback)
0 commit comments