当前位置:   article > 正文

nvidia-cuda-mps-control mps 参数介绍_nvidia-cuda-mps-control windows

nvidia-cuda-mps-control windows
  1. 1. 功能
  2. nvidia-cuda-mps-control - NVIDIA CUDA Multi Process Service management program
  1. 2. 启动
  2. nvidia-cuda-mps-control -d
  1. 3. 描述
  2. MPS is a runtime service designed to let multiple MPI processes using CUDA to run
  3. concurrently on a single GPU in a way that's transparent to the MPI program. A CUDA
  4. program runs in MPS mode if the MPS control daemon is running on the system.
  5. When CUDA is first initialized in a program, the CUDA driver attempts to connect to the
  6. MPS control daemon. If the connection attempt fails, the program continues to run as it
  7. normally would without MPS. If however, the connection attempt to the control daemon
  8. succeeds, the CUDA driver then requests the daemon to start an MPS server on its behalf.
  9. If there's an MPS server already running, and the user id of that server process matches
  10. that of the requesting client process, the control daemon simply notifies the client
  11. process of it, which then proceeds to connect to the server. If there's no MPS server
  12. already running on the system, the control daemon launches an MPS server with the same
  13. user id (UID) as that of the requesting client process. If there's an MPS server already
  14. running, but with a different user id than that of the client process, the control daemon
  15. requests the existing server to shutdown as soon as all its clients are done. Once the
  16. existing server has terminated, the control daemon launches a new server with the user id
  17. same as that of the queued client process.
  18. The MPS server creates the shared GPU context, manages its clients, and issues work to the
  19. GPU on behalf of its clients. An MPS server can support upto 16 client CUDA contexts at a
  20. time. MPS is transparent to CUDA programs, with all the complexity of communication
  21. between the client process, the server and the control daemon hidden within the driver
  22. binaries.
  23. Currently, CUDA MPS is available on 64-bit Linux only, requires a device that supports
  24. Unified Virtual Address (UVA) and has compute capability SM 3.5 or higher. Applications
  25. requiring pre-CUDA 4.0 APIs are not supported under CUDA MPS. MPS is also not supported
  26. on multi-GPU configurations. Please use CUDA_VISIBLE_DEVICES when starting the control
  27. daemon to limit visibility to a single device.
  1. 4 选项
  2. -d
  3. Start the MPS control daemon, assuming the user has enough privilege (e.g. root).
  4. -h, --help
  5. Print a help message.
  6. <no arguments>
  7. Start the front-end management user interface to the MPS control daemon, which needs to be
  8. started first. The front-end UI keeps reading commands from stdin until EOF. Commands are
  9. separated by the newline character. If an invalid command is issued and rejected, an error
  10. message will be printed to stdout. The exit status of the front-end UI is zero if
  11. communication with the daemon is successful. A non-zero value is returned if the daemon is
  12. not found or connection to the daemon is broken unexpectedly. See the "quit" command below
  13. for more information about the exit status.
  14. Commands supported by the MPS control daemon:
  15. get_server_list
  16. Print out a list of PIDs of all MPS servers.
  17. start_server -uid UID
  18. Start a new MPS server for the specified user (UID).
  19. shutdown_server PID [-f]
  20. Shutdown the MPS server with given PID. The MPS server will not accept any new
  21. client connections and it exits when all current clients disconnect. -f is forced
  22. immediate shutdown. If a client launches a faulty kernel that runs forever, a
  23. forced shutdown of the MPS server may be required, since the MPS server creates and
  24. issues GPU work on behalf of its clients.
  25. get_client_list PID
  26. Print out a list of PIDs of all clients connected to the MPS server with given PID.
  27. quit [-t TIMEOUT]
  28. Shutdown the MPS control daemon process and all MPS servers. The MPS control daemon
  29. stops accepting new clients while waiting for current MPS servers and MPS clients
  30. to finish. If TIMEOUT is specified (in seconds), the daemon will force MPS servers
  31. to shutdown if they are still running after TIMEOUT seconds.
  32. This command is synchronous. The front-end UI waits for the daemon to shutdown,
  33. then returns the daemon's exit status. The exit status is zero iff all MPS servers
  34. have exited gracefully.
  1. 5. 环境
  2. CUDA_MPS_PIPE_DIRECTORY
  3. Specify the directory that contains the named pipes used for communication among
  4. MPS control, MPS server, and MPS clients. The value of this environment variable
  5. should be consistent in the MPS control daemon and all MPS client processes.
  6. Default directory is /tmp/nvidia-mps
  7. CUDA_MPS_LOG_DIRECTORY
  8. Specify the directory that contains the MPS log files. This variable is used by the
  9. MPS control daemon only. Default directory is /var/log/nvidia-mps
  1. 6. 文件
  2. Log files created by the MPS control daemon in the specified directory
  3. control.log
  4. Record startup and shutdown of MPS control daemon, user commands issued with their
  5. results, and status of MPS servers.
  6. server.log
  7. Record startup and shutdown of MPS servers, and status of MPS clients.

 

声明:本文内容由网友自发贡献,不代表【wpsshop博客】立场,版权归原作者所有,本站不承担相应法律责任。如您发现有侵权的内容,请联系我们。转载请注明出处:https://www.wpsshop.cn/w/我家小花儿/article/detail/963335
推荐阅读
相关标签
  

闽ICP备14008679号