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
feat(gds): add gds_path_sharding config for multi-path strategy
Add a top-level `gds_path_sharding` config field (default: "by_gpu")
that controls how GPUs are assigned to storage paths when multiple
comma-separated paths are provided in `gds_path`. This replaces the
previously hardcoded by_gpu logic with an explicit, extensible setting.
Currently only "by_gpu" is supported (selects path via
`device_id % num_paths`); unsupported values raise AssertionError.
Generated with [Devin](https://cli.devin.ai/docs)
Co-Authored-By: Devin <noreply@cognition.ai>
Signed-off-by: Boris Glimcher <Boris.Glimcher@emc.com>
Copy file name to clipboardExpand all lines: docs/source/api_reference/configurations.rst
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -341,7 +341,10 @@ Settings for different storage backends and paths.
341
341
- Description
342
342
* - gds_path
343
343
- LMCACHE_GDS_PATH
344
-
- Path for GDS backend. Supports comma-separated paths for multi-device I/O (e.g. ``/mnt/nvme0/cache,/mnt/nvme1/cache``). Each GPU selects a path via ``device_id % num_paths``.
344
+
- Path for GDS backend. Supports comma-separated paths for multi-device I/O (e.g. ``/mnt/nvme0/cache,/mnt/nvme1/cache``). See ``gds_path_sharding`` for how paths are assigned to GPUs.
345
+
* - gds_path_sharding
346
+
- LMCACHE_GDS_PATH_SHARDING
347
+
- Strategy for selecting a path when multiple paths are provided. Currently only ``"by_gpu"`` is supported, which selects paths based on GPU device ID (default: "by_gpu").
0 commit comments