Cuda nvidia smi-以NVML表示的交流等效物

我了解到nvidia smi-ac可以用来改变时钟 GPU内核和内存的速率。nvidia smi是基于NVML库构建的吗？ 自从我检查文档以来，它在NVML中的等价物是什么

但只能看到用于获取时钟速率值的API，而不是 设置它们

---

谢谢

是的，nvidia smi是基于NVML库构建的

根据可用的最新nvml api文档（链接自我之前向您推荐的站点），特斯拉K10和K20 GPU上支持“设置应用程序时钟”命令（第6页）。我相信Quadro家族的“开普勒”成员也支持它，比如Quadro K5000

如果您有特斯拉K10、K20或K20X GPU，则在p68中描述了设置应用程序时钟命令，为了方便起见，我在这里也复制了该命令：

7.12.2.2 nvmlReturn_t DECLDIR nvmlDeviceSetApplicationsClocks (nvmlDevice_t device, unsigned int
memClockMHz, unsigned int graphicsClockMHz)

Set clocks that applications will lock to.
Sets the clocks that compute and graphics applications will be running at. e.g. CUDA driver requests these clocks
during context creation which means this property defines clocks at which CUDA applications will be running unless
some overspec event occurs (e.g. over power, over thermal or external HW brake).
Can be used as a setting to request constant performance.
For Tesla ™products, and Quadro ®products from the Kepler family. Requires root/admin permissions.
See nvmlDeviceGetSupportedMemoryClocks and nvmlDeviceGetSupportedGraphicsClocks for details on how to list
available clocks combinations.
After system reboot or driver reload applications clocks go back to their default value.

Parameters:
device The identifier of the target device
memClockMHz Requested memory clock in MHz
graphicsClockMHz Requested graphics clock in MHz

Returns:
• NVML_SUCCESS if new settings were successfully set
• NVML_ERROR_UNINITIALIZED if the library has not been successfully initialized
• NVML_ERROR_INVALID_ARGUMENT if device is invalid or memClockMHz and graphicsClockMHz is
not a valid clock combination
• NVML_ERROR_NO_PERMISSION if the user doesn’t have permission to perform this operation
• NVML_ERROR_NOT_SUPPORTED if the device doesn’t support this feature
• NVML_ERROR_UNKNOWN on any unexpected error

---

是的，nvidia smi构建在NVML库上

根据可用的最新nvml api文档（链接自我之前向您推荐的站点），特斯拉K10和K20 GPU上支持“设置应用程序时钟”命令（第6页）。我相信Quadro家族的“开普勒”成员也支持它，比如Quadro K5000

如果您有特斯拉K10、K20或K20X GPU，则在p68中描述了设置应用程序时钟命令，为了方便起见，我在这里也复制了该命令：

7.12.2.2 nvmlReturn_t DECLDIR nvmlDeviceSetApplicationsClocks (nvmlDevice_t device, unsigned int
memClockMHz, unsigned int graphicsClockMHz)

Set clocks that applications will lock to.
Sets the clocks that compute and graphics applications will be running at. e.g. CUDA driver requests these clocks
during context creation which means this property defines clocks at which CUDA applications will be running unless
some overspec event occurs (e.g. over power, over thermal or external HW brake).
Can be used as a setting to request constant performance.
For Tesla ™products, and Quadro ®products from the Kepler family. Requires root/admin permissions.
See nvmlDeviceGetSupportedMemoryClocks and nvmlDeviceGetSupportedGraphicsClocks for details on how to list
available clocks combinations.
After system reboot or driver reload applications clocks go back to their default value.

Parameters:
device The identifier of the target device
memClockMHz Requested memory clock in MHz
graphicsClockMHz Requested graphics clock in MHz

Returns:
• NVML_SUCCESS if new settings were successfully set
• NVML_ERROR_UNINITIALIZED if the library has not been successfully initialized
• NVML_ERROR_INVALID_ARGUMENT if device is invalid or memClockMHz and graphicsClockMHz is
not a valid clock combination
• NVML_ERROR_NO_PERMISSION if the user doesn’t have permission to perform this operation
• NVML_ERROR_NOT_SUPPORTED if the device doesn’t support this feature
• NVML_ERROR_UNKNOWN on any unexpected error

---

VaibhavSundriyal：你应该考虑接受这个答案。@ VaibhavSundriyal：你应该考虑接受这个答案。