11 releases (7 breaking)

0.8.0 Feb 10, 2024
0.7.0 Jan 21, 2023
0.6.0 May 27, 2022
0.5.0 Dec 7, 2020
0.3.0 Jul 20, 2017

#288 in Hardware support

Download history 6143/week @ 2024-03-14 5910/week @ 2024-03-21 6450/week @ 2024-03-28 5761/week @ 2024-04-04 6791/week @ 2024-04-11 6566/week @ 2024-04-18 7006/week @ 2024-04-25 8020/week @ 2024-05-02 6636/week @ 2024-05-09 5698/week @ 2024-05-16 6788/week @ 2024-05-23 7160/week @ 2024-05-30 6668/week @ 2024-06-06 8093/week @ 2024-06-13 7961/week @ 2024-06-20 5970/week @ 2024-06-27

29,925 downloads per month
Used in 26 crates (3 directly)




Crates.io version Crates.io downloads Docs.rs docs

Rust bindings for the NVIDIA Management Library (NVML), a C-based programmatic interface for monitoring and managing various states within NVIDIA GPUs.

It is intended to be a platform for building 3rd-party applications, and is also the underlying library for NVIDIA's nvidia-smi tool.

See nvml-wrapper for a safe wrapper over top of these bindings.

Type of Bindings

These bindings were created using bindgen's feature to generate wrappers over top of the functionality that the libloading crate provides. This means that they're designed for loading the NVML library at runtime; they are not suitable for linking to NVML (statically or dynamically) at buildtime.

This choice was made because NVML is the type of library that you'd realistically always want to load at runtime, for the following reasons:

  • NVIDIA doesn't distribute static versions of NVML, so it isn't possible to statically link it anyway
  • Linking to NVML at buildtime means the resulting binary can only be run on systems that have NVIDIA GPUs and well-formed NVIDIA driver installs

Loading NVML at runtime means it's possible to drop NVIDIA-related features at runtime on systems that don't have relevant hardware.

I would be willing to consider maintaining both types of bindings in this crate if there's a convincing reason to do so; please file an issue.

NVML Support

These bindings were generated for NVML version 11. Each new version of NVML is guaranteed to be backwards-compatible according to NVIDIA, so these bindings should be useful regardless of NVML version bumps.

Legacy Functions

Sometimes there will be function-level API version bumps in new NVML releases. For example:


The older versions of the functions will generally continue to work with the newer NVML releases; however, the newer function versions will not work with older NVML installs.

By default these bindings only include the newest versions of the functions. Enable the legacy-functions feature if you require the ability to call older functions.


Licensed under either of Apache License, Version 2.0 or MIT license at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in this crate by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.