Repository navigation
feat(cli): manage user-owned CUDA MPS daemons - #2085
Merged
Merged
Conversation
TATP-233
force-pushed
the
feat/issue-2079-cuda-mps-cli
branch
2 times, most recently
from
October 8, 2026 13:20
c2d1d8a to
b9b0ad5
Compare
TATP-233
force-pushed
the
feat/issue-2079-cuda-mps-cli
branch
from
October 8, 2026 13:38
b9b0ad5 to
5222087
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Driving issue
Closes #2079.
Final UX
The MPS lifecycle is a short, flat command. On the supported single-GPU host, no arguments are required:
Read-only host inspection:
Explicit overrides remain for multi-GPU selection, stable labels, and service-owned paths:
Defaults
gpu-<uuid-prefix>~/.cache/unilab/cuda-mps/<name>/pipe~/.cache/unilab/cuda-mps/<name>/logenv/stoptargetAmbiguity does not silently select a target:
--gpus;--name;Delivered behavior
uni-cumpspackage entrypoint, owned bysrc/unilab/training/cuda_mps_cli.py.status,doctor,start,stop,stop --all, andenv.single_gpu,single_task_multi_gpu, andtask_per_gpu.single_gpu; multi-GPU/all daemon execution fails closed and points to CUDA MPS under multi-GPU DP: evidence gaps and design constraints #2063/roadmap: multi-GPU tensor runtime scaling (M10) #1672.~/.cache/unilab/cuda-mps/<name>/daemon.json.(UID, hostname, name)./proc/<pid>/statstart-time.(nvidia-cuda-mps)do not break stop authority.nvidia-smiUUID spelling, including hyphens and case, for CUDA visibility masks.doctorselects the sole matching live managed daemon and probes its pipe/log environment.training.cuda_process_sharing=mpsremains explicit, with noautomode and no implicit daemon selection.Impact
Validation
Commands run on final local head
52220875:Results:
1847 passed, 42 skipped, 488 deselected;34/34, script-mode35/35.Focused checks:
Result:
69 passed.Sphinx strict build was run successfully with no warning introduced by this change.
Real Linux/NVIDIA lifecycle smoke
Completed on the available host with a real
nvidia-cuda-mps-control:Observed:
startwrote a record containing PID2578762, procfs start-time131179025, canonical UUID, UID, host, and absolute pipe/log paths.doctorselected the live managed daemon and reportedvalid=True.statusreported the daemon live.envemitted the correctCUDA_VISIBLE_DEVICES, pipe, and log exports.stopreturned 0 and removed the record.statusreportedmanaged_daemons=none; the control process was no longer present.Regression coverage added from this real run:
commparsing;Scope boundaries / limitations
single_task_multi_gpuandtask_per_gpuare contract names only; execution remains blocked pending CUDA MPS under multi-GPU DP: evidence gaps and design constraints #2063/roadmap: multi-GPU tensor runtime scaling (M10) #1672 and a lease/reference model.