The following list describes all possible data returned by the -q device query option. Unless otherwise
noted all numerical results are base 10 and unitless.
Timestamp
The current system timestamp at the time nvidia-smi was invoked. Format is "Day-of-week Month Day
HH:MM:SS Year".
DriverVersion
The version of the installed NVIDIA display driver. This is an alphanumeric string.
CUDAVersion
The version of the CUDA toolkit installed on the system. This is an alphanumeric string.
AttachedGPUs
The number of NVIDIA GPUs in the system.
ProductName
The official product name of the GPU. This is an alphanumeric string. For all products.
ProductBrand
The official brand of the GPU. This is an alphanumeric string. For all products.
ProductArchitecture
The official architecture name of the GPU. This is an alphanumeric string. For all products.
DisplayMode
This field is deprecated, and will be removed in a future release.
DisplayAttached
A flag that indicates whether a physical display (e.g. monitor) is currently connected to any of the
GPU's connectors. "Yes" indicates an attached display. "No" indicates otherwise.
DisplayActive
A flag that indicates whether a display is initialized on the GPU's (e.g. memory is allocated on the
device for display). Display can be active even when no monitor is physically attached. "Enabled"
indicates an active display. "Disabled" indicates otherwise.
PersistenceMode
A flag that indicates whether persistence mode is enabled for the GPU. Value is either "Enabled" or
"Disabled". When persistence mode is enabled the NVIDIA driver remains loaded even when no active
clients, such as X11 or nvidia-smi, exist. This minimizes the driver load latency associated with running
dependent apps, such as CUDA programs. For all CUDA-capable products. Linux only.
AddressingMode
A field that indicates which addressing mode is currently active. The value is "ATS" or "HMM" or "None".
When the mode is "ATS", system allocated memory like malloc is addressable from the GPU via Address
Translation Services. This means there is effectively a single set of page tables used by both the CPU
and the GPU. When the mode is "HMM", system allocated memory like malloc is addressable from the GPU via
software-based mirroring of the CPU's page tables, on the GPU. When the mode is "None", neither ATS nor
HMM is active. Linux only.
MIGMode
MIG Mode configuration status
Current MIG mode currently in use - NA/Enabled/Disabled
Pending Pending configuration of MIG Mode - Enabled/Disabled
AccountingMode
A flag that indicates whether accounting mode is enabled for the GPU. Value is either "Enabled" or
"Disabled". When accounting is enabled statistics are calculated for each compute process running on the
GPU. Statistics can be queried during the lifetime or after termination of the process. The execution
time of process is reported as 0 while the process is in running state and updated to actual execution
time after the process has terminated. See --help-query-accounted-apps for more info.
AccountingModeBufferSize
Returns the size of the circular buffer that holds list of processes that can be queried for accounting
stats. This is the maximum number of processes that accounting information will be stored for before
information about oldest processes will get overwritten by information about new processes.
DriverModel
On Windows, the TCC and WDDM driver models are supported. The driver model can be changed with the (-dm)
or (-fdm) flags. The TCC driver model is optimized for compute applications. I.E. kernel launch times
will be quicker with TCC. The WDDM driver model is designed for graphics applications and is not
recommended for compute applications. Linux does not support multiple driver models, and will always have
the value of "N/A".
Current The driver model currently in use. Always "N/A" on Linux.
Pending The driver model that will be used on the next reboot. Always "N/A" on Linux.
SerialNumber
This number matches the serial number physically printed on each board. It is a globally unique immutable
alphanumeric value.
GPUUUID
This value is the globally unique immutable alphanumeric identifier of the GPU. It does not correspond to
any physical label on the board.
MinorNumber
The minor number for the device is such that the Nvidia device node file for each GPU will have the form
/dev/nvidia[minor number]. Available only on Linux platform.
VBIOSVersion
The BIOS of the GPU board.
MultiGPUBoard
Whether or not this GPU is part of a multiGPU board.
BoardID
The unique board ID assigned by the driver. If two or more GPUs have the same board ID and the above
"MultiGPU" field is true then the GPUs are on the same board.
BoardPartNumber
The unique part number of the GPU's board
GPUPartNumber
The unique part number of the GPU
FRUPartNumber
Unique FRU part number of the GPU
PlatformInfo
Platform Information are compute tray platform specific information. They are GPU's positional index and
platform identifying information.
ChassisSerialNumber
Serial Number of the chassis containing this GPU.
SlotNumber
The slot number in the chassis containing this GPU (includes switches).
TrayIndex
The tray index within the compute slots in the chassis containing this GPU (does not include switches).
HostID
Index of the node within the slot containing this GPU.
PeerType
Platform indicated NVLink-peer type (e.g. switch present or not).
ModuleId
ID of this GPU within the node.
GPUFabricGUID
Fabric ID for this GPU.
InforomVersion
Version numbers for each object in the GPU board's inforom storage. The inforom is a small, persistent
store of configuration and state data for the GPU. All inforom version fields are numerical. It can be
useful to know these version numbers because some GPU features are only available with inforoms of a
certain version or higher.
If any of the fields below return Unknown Error additional Inforom verification check is performed and
appropriate warning message is displayed.
ImageVersion Global version of the infoROM image. Image version just like VBIOS version uniquely
describes the exact version of the infoROM flashed on the board in contrast to infoROM
object version which is only an indicator of supported features.
OEMObject Version for the OEM configuration data.
ECCObject Version for the ECC recording data.
PowerManagementObject
Version for the power management data.
Inforomchecksumvalidation
Inforom checksum validation ("valid", "invalid", "N/A") Only available via --query-gpu
inforom.checksum_validation
InforomBBXObjectFlush
Information about flushing of the blackbox data to the inforom storage.
LatestTimestamp
The timestamp of the latest flush of the BBX Object during the current run.
LatestDuration
The duration of the latest flush of the BBX Object during the current run.
GPUOperationMode
GOM allows one to reduce power usage and optimize GPU throughput by disabling GPU features.
Each GOM is designed to meet specific user needs.
In "All On" mode everything is enabled and running at full speed.
The "Compute" mode is designed for running only compute tasks. Graphics operations are not allowed.
The "Low Double Precision" mode is designed for running graphics applications that don't require high
bandwidth double precision.
GOM can be changed with the (--gom) flag.
Supported on GK110 M-class and X-class Tesla products from the Kepler family. Not supported on Quadro and
Tesla C-class products. Low Double Precision and All On modes are the only modes available for supported
GeForce Titan products.
Current The GOM currently in use.
Pending The GOM that will be used on the next reboot.
GPUC2CMode
The C2C mode of the GPU.
GPUResetStatus
Reset status of the GPU. This functionality is deprecated.
ResetRequired Requested functionality has been deprecated
DrainandResetRecommended
Requested functionality has been deprecated
GPURecoveryAction
Action to take to clear fault that previously happened. It is not intended for determining which fault
triggered recovery action.
Possible values: None, Reset, Reboot, Drain P2P, Drain and Reset
None
No recovery action needed
Reset
Example scenario - Uncontained HBM/SRAM UCE
The GPU has encountered a fault that requires a reset to recover.
Terminate all GPU processes, reset the GPU using 'nvidia-smi -r', and the GPU can be used again by
starting new GPU processes.
Reboot
Example scenario - UVM fatal error
The GPU has encountered a fault may have left the OS in an inconsistent state.
Reboot the operating system to restore the OS back to a consistent state.
Node reboot required.
Application cannot restart without node reboot
OS warm reboot is sufficient (no need for AC/DC cycle)
DrainP2P
Example scenario - N/A
The GPU has encountered a fault that requires all peer-to-peer traffic to be quiesced.
Terminate all GPU processes that conduct peer-to-peer traffic and disable UVM persistence mode.
Disable job scheduling (no new jobs), stop all applications when convenient, if persistence mode is
enabled, disable it
Once all peer-to-peer traffic are drained, query NVML_FI_DEV_GET_GPU_RECOVERY_ACTION again, which will
return one of the other actions.
If still DRAIN_P2P, then GPU reset.
DrainandReset
Example scenario - Contained HBM UCE
Reset Recommended.
The GPU has encountered a fault that results the GPU to temporarily operate at a reduced capacity, such
as part of its frame buffer memory being offlined, or some of its MIG partitions down.
No new work should be scheduled on the GPU, but existing work that didn’t get affected are safe to
continue until they finish or reach a good checkpoint.
Safe to restart application (memory capacity will be reduced due to dynamic page offlining), but need to
eventually reset (to get row remap).
Asserted only for UCE row remaps.
After all existing work have drained, reset the GPU to regain its full capacity.
GSPFirmwareVersion
Firmware version of GSP. This is an alphanumeric string.
PCI
Basic PCI info for the device. Some of this information may change whenever cards are added/removed/moved
in a system. For all products.
Bus PCI bus number, in hex
Device PCI device number, in hex
Domain PCI domain number, in hex
BaseClasscode PCI Base classcode, in hex
SubClasscode PCI Sub classcode, in hex
DeviceId PCI vendor device id, in hex
SubSystemId PCI Sub System id, in hex
BusId PCI bus id as "domain:bus:device.function", in hex
GPULinkinformation
The PCIe link generation and bus width
Current The current link generation and width. These may be reduced when the GPU is not in use.
Max The maximum link generation and width possible with this GPU and system configuration. For
example, if the GPU supports a higher PCIe generation than the system supports then this
reports the system PCIe generation.
BridgeChip
Information related to Bridge Chip on the device. The bridge chip firmware is only present on certain
boards and may display "N/A" for some newer multiGPUs boards.
Type The type of bridge chip. Reported as N/A if doesn't exist.
FirmwareVersion
The firmware version of the bridge chip. Reported as N/A if doesn't exist.
ReplaysSinceReset
The number of PCIe replays since reset.
ReplayNumberRollovers
The number of PCIe replay number rollovers since reset. A replay number rollover occurs after 4
consecutive replays and results in retraining the link.
TxThroughput
The GPU-centric transmission throughput across the PCIe bus in MB/s over the past 20ms. Only supported on
Maxwell architectures and newer.
RxThroughput
The GPU-centric receive throughput across the PCIe bus in MB/s over the past 20ms. Only supported on
Maxwell architectures and newer.
AtomicCaps
The PCIe atomic capabilities of outbound/inbound operations of the GPU.
FanSpeed
The fan speed value is the percent of the product's maximum noise tolerance fan speed that the device's
fan is currently intended to run at. This value may exceed 100% in certain cases. Note: The reported
speed is the intended fan speed. If the fan is physically blocked and unable to spin, this output will
not match the actual fan speed. Many parts do not report fan speeds because they rely on cooling via fans
in the surrounding enclosure. For all discrete products with dedicated fans.
PerformanceState
The current performance state for the GPU. States range from P0 (maximum performance) to P12 (minimum
performance).
ClocksEventReasons
Retrieves information about factors that are reducing the frequency of clocks.
If all event reasons are returned as "Not Active" it means that clocks are running as high as possible.
Idle Nothing is running on the GPU and the clocks are dropping to Idle state. This limiter may
be removed in a later release.
ApplicationClocksSetting
GPU clocks are limited by applications clocks setting. E.g. can be changed using nvidia-
smi --applications-clocks=
SWPowerCap SW Power Scaling algorithm is reducing the clocks below requested clocks because the GPU
is consuming too much power. E.g. SW power cap limit can be changed with nvidia-smi
--power-limit=
HWSlowdown HW Slowdown (reducing the core clocks by a factor of 2 or more) is engaged. HW Thermal
Slowdown and HW Power Brake will be displayed on Pascal+.
This is an indicator of:\
• Temperature being too high (HW Thermal Slowdown)\
• External Power Brake Assertion is triggered (e.g. by the system power supply) (HW Power Brake
Slowdown)\
• Power draw is too high and Fast Trigger protection is reducing the clocks
SWThermalSlowdown
SW Thermal capping algorithm is reducing clocks below requested clocks because GPU
temperature is higher than Max Operating Temp
ClockEventReasonsCounters
Counters, in microseconds, for the amount of time factors have been reducing the frequency of clocks
SWPowerCapping
Amount of time SW Power Scaling algorithm has reduced the clocks below requested clocks
because the GPU was consuming too much power.
SyncBoostGroup
Amount of time the clock frequency of this GPU was reduced to match the minimum possible
clock across the sync boost group.
SWThermalSlowdown
Amount of time SW Thermal capping algorithm has reduced clocks below requested clocks
because GPU temperature was higher than Max Operating Temp.
HWThermalSlowdown
Amount of time HW Thermal Slowdown was engaged, reducing the core clocks by a factor of 2
or more, due to temperature being too high.
HWPowerBraking
Amount of time External Power Brake Assertion was triggered (e.g. by the system power
supply).
SparseOperationMode
A flag that indicates whether sparse operation mode is enabled for the GPU. Value is either "Enabled" or
"Disabled". Reported as "N/A" if not supported.
FBMemoryUsage
On-board frame buffer memory information. Reported total memory can be affected by ECC state. If ECC does
affect the total available memory, memory is decreased by several percent, due to the requisite parity
bits. The driver may also reserve a small amount of memory for internal use, even without active work on
the GPU. On systems where GPUs are NUMA nodes, the accuracy of FB memory utilization provided by nvidia-
smi depends on the memory accounting of the operating system. This is because FB memory is managed by the
operating system instead of the NVIDIA GPU driver. Typically, pages allocated from FB memory are not
released even after the process terminates to enhance performance. In scenarios where the operating
system is under memory pressure, it may resort to utilizing FB memory. Such actions can result in
discrepancies in the accuracy of memory reporting. For all products.
Total Total size of FB memory.
Reserved Reserved size of FB memory.
Used Used size of FB memory.
Free Available size of FB memory.
BAR1MemoryUsage
BAR1 is used to map the FB (device memory) so that it can be directly accessed by the CPU or by 3rd party
devices (peer-to-peer on the PCIe bus).
Total Total size of BAR1 memory.
Used Used size of BAR1 memory.
Free Available size of BAR1 memory.
ComputeMode
The compute mode flag indicates whether individual or multiple compute applications may run on the GPU.
"Default" means multiple contexts are allowed per device.
"Exclusive Process" means only one context is allowed per device, usable from multiple threads at a time.
"Prohibited" means no contexts are allowed per device (no compute apps).
"EXCLUSIVE_PROCESS" was added in CUDA 4.0. Prior CUDA releases supported only one exclusive mode, which
is equivalent to "EXCLUSIVE_THREAD" in CUDA 4.0 and beyond.
For all CUDA-capable products.
Utilization
Utilization rates report how busy each GPU is over time, and can be used to determine how much an
application is using the GPUs in the system. Note: On MIG-enabled GPUs, querying the utilization of
encoder, decoder, jpeg, ofa, gpu, and memory is not currently supported.
Note: During driver initialization when ECC is enabled one can see high GPU and Memory Utilization
readings. This is caused by ECC Memory Scrubbing mechanism that is performed during driver
initialization.
GPU Percent of time over the past sample period during which one or more kernels was executing
on the GPU. The sample period may be between 1 second and 1/6 second depending on the
product.
Memory Percent of time over the past sample period during which global (device) memory was being
read or written. The sample period may be between 1 second and 1/6 second depending on the
product.
Encoder Percent of time over the past sample period during which the GPU's video encoder was being
used. The sampling rate is variable and can be obtained directly via the
nvmlDeviceGetEncoderUtilization() API
Decoder Percent of time over the past sample period during which the GPU's video decoder was being
used. The sampling rate is variable and can be obtained directly via the
nvmlDeviceGetDecoderUtilization() API
JPEG Percent of time over the past sample period during which the GPU's JPEG decoder was being
used. The sampling rate is variable and can be obtained directly via the
nvmlDeviceGetJpgUtilization() API
OFA Percent of time over the past sample period during which the GPU's OFA (Optical Flow
Accelerator) was being used. The sampling rate is variable and can be obtained directly
via the nvmlDeviceGetOfaUtilization() API
EncoderStats
Encoder Stats report the count of active encoder sessions, along with the average Frames Per Second (FPS)
and average latency (in microseconds) for all these active sessions on this device.
ActiveSessions
The total number of active encoder sessions on this device.
AverageFPS The average Frame Per Sencond (FSP) of all active encoder sessions on this device.
AverageLatency
The average latency in microseconds of all active encoder sessions on this device.
DRAMEncryptionMode
A flag that indicates whether DRAM Encryption support is enabled. May be either "Enabled" or "Disabled".
Changes to DRAM Encryption mode require a reboot. Requires Inforom ECC object.
Current The DRAM Encryption mode that the GPU is currently operating under.
Pending The DRAM Encryption mode that the GPU will operate under after the next reboot.
ECCMode
A flag that indicates whether ECC support is enabled. May be either "Enabled" or "Disabled". Changes to
ECC mode require a reboot. Requires Inforom ECC object version 1.0 or higher.
Current The ECC mode that the GPU is currently operating under.
Pending The ECC mode that the GPU will operate under after the next reboot.
ECCErrors
NVIDIA GPUs can provide error counts for various types of ECC errors. Some ECC errors are either single
or double bit, where single bit errors are corrected and double bit errors are uncorrectable. Texture
memory errors may be correctable via resend or uncorrectable if the resend fails. These errors are
available across two timescales (volatile and aggregate). Single bit ECC errors are automatically
corrected by the HW and do not result in data corruption. Double bit errors are detected but not
corrected. Please see the ECC documents on the web for information on compute application behavior when
double bit errors occur. Volatile error counters track the number of errors detected since the last
driver load. Aggregate error counts persist indefinitely and thus act as a lifetime counter.
A note about volatile counts: On Windows this is once per boot. On Linux this can be more frequent. On
Linux the driver unloads when no active clients exist. Hence, if persistence mode is enabled or there is
always a driver client active (e.g. X11), then Linux also sees per-boot behavior. If not, volatile counts
are reset each time a compute app is run.
Tesla and Quadro products pre-volta can display total ECC error counts, as well as a breakdown of errors
based on location on the chip. The locations are described below. Location-based data for aggregate error
counts requires Inforom ECC object version 2.0. All other ECC counts require ECC object version 1.0.
DeviceMemory Errors detected in global device memory.
RegisterFile Errors detected in register file memory.
L1Cache Errors detected in the L1 cache.
L2Cache Errors detected in the L2 cache.
TextureMemory Parity errors detected in texture memory.
Total Total errors detected across entire chip. Sum of DeviceMemory, RegisterFile, L1Cache,
L2Cache and TextureMemory.
On Turing the output is such:
SRAMCorrectable
Number of correctable errors detected in any of the SRAMs
SRAMUncorrectable
Number of uncorrectable errors detected in any of the SRAMs
DRAMCorrectable
Number of correctable errors detected in the DRAM
DRAMUncorrectable
Number of uncorrectable errors detected in the DRAM
On Ampere+ The categorization of SRAM errors has been expanded upon. SRAM errors are now categorized as
either parity or SEC-DED (single error correctable/double error detectable) depending on which unit hit
the error. A histogram has been added that categorizes what unit hit the SRAM error. Additionally a flag
has been added that indicates if the threshold for the specific SRAM has been exceeded.
SRAMUncorrectableParity
Number of uncorrectable errors detected in SRAMs that are parity protected
SRAMUncorrectableSEC-DED
Number of uncorrectable errors detected in SRAMs that are SEC-DED protected
AggregateUncorrectableSRAMSourcesSRAML2 Errors that occurred in the L2 cache
SRAMSM Errors that occurred in the SM
SRAMMicrocontroller
Errors that occurred in a microcontroller (PMU/GSP etc...)
SRAMPCIE Errors that occrred in any PCIE related unit
SRAMOther Errors occuring in anything else not covered above
PageRetirement
NVIDIA GPUs can retire pages of GPU device memory when they become unreliable. This can happen when
multiple single bit ECC errors occur for the same page, or on a double bit ECC error. When a page is
retired, the NVIDIA driver will hide it such that no driver, or application memory allocations can access
it.
DoubleBitECC The number of GPU device memory pages that have been retired due to a double bit ECC
error.
SingleBitECC The number of GPU device memory pages that have been retired due to multiple single bit
ECC errors.
Pending Checks if any GPU device memory pages are pending blacklist on the next reboot. Pages that are
retired but not yet blacklisted can still be allocated, and may cause further reliability issues.
RowRemapper
NVIDIA GPUs can remap rows of GPU device memory when they become unreliable. This can happen when a
single uncorrectable ECC error or multiple correctable ECC errors occur on the same row. When a row is
remapped, the NVIDIA driver will remap the faulty row to a reserved row. All future accesses to the row
will access the reserved row instead of the faulty row. This feature is available on Ampere+
CorrectableError The number of rows that have been remapped due to correctable ECC errors.
UncorrectableError The number of rows that have been remapped due to uncorrectable ECC errors.
Pending Indicates whether or not a row is pending remapping. The GPU must be reset for the remapping to
go into effect.
RemappingFailureOccurred Indicates whether or not a row remapping has failed in the past.
BankRemapAvailabilityHistogram Each memory bank has a fixed number of reserved rows that can be used
for row remapping. The histogram will classify the remap availability of each bank into Maximum, High,
Partial, Low and None. Maximum availability means that all reserved rows are available for remapping
while None means that no reserved rows are available. Correctable row remappings don't count towards the
availability histogram since row remappings due to correctable row remappings can be evicted by an
uncorrectable row remapping.
Temperature
Readings from temperature sensors on the board. All readings are in degrees C. Not all products support
all reading types. In particular, products in module form factors that rely on case fans or passive
cooling do not usually provide temperature readings. See below for restrictions.
T.Limit: The T.Limit sensor measures the current margin in degree Celsius to the maximum operating
temperature. As such it is not an absolute temperature reading rather a relative measurement.
Not all products support T.Limit sensor readings.
When supported, nvidia-smi reports the current T.Limit temperature as a signed value that counts down. A
T.Limit temperature of 0 C or lower indicates that the GPU may optimize its clock based on thermal
conditions. Further, when the T.Limit sensor is supported, available temperature thresholds are also
reported relative to T.Limit (see below) instead of absolute measurements.
GPU Core GPU temperature. For all discrete and S-class products.
T.LimitTemp Current margin in degrees Celsius from the maximum GPU operating temperature.
ShutdownTemp The temperature at which a GPU will shutdown.
ShutdownT.LimitTemp
The T.Limit temperature below which a GPU may shutdown. Since shutdown can only triggered
by the maximum GPU temperature it is possible for the current T.Limit to be more negative
than this threshold.
SlowdownTemp The temperature at which a GPU HW will begin optimizing clocks due to thermal conditions,
in order to cool.
SlowdownT.LimitTemp
The T.Limit temperature below which a GPU HW may optimize its clocks for thermal
conditions. Since this clock adjustment can only triggered by the maximum GPU temperature
it is possible for the current T.Limit to be more negative than this threshold.
MaxOperatingTemp
The temperature at which GPU SW will optimize its clock for thermal conditions.
MaxOperatingT.LimitTemp
The T.Limit temperature below which GPU SW will optimize its clock for thermal conditions.
PowerReadings
Power readings help to shed light on the current power usage of the GPU, and the factors that affect that
usage. When power management is enabled the GPU limits power draw under load to fit within a predefined
power envelope by manipulating the current performance state. See below for limits of availability.
Please note that power readings are not applicable for Pascal and higher GPUs with BA sensor boards.
PowerState Power State is deprecated and has been renamed to Performance State in 2.285. To maintain
XML compatibility, in XML format Performance State is listed in both places.
PowerManagement
A flag that indicates whether power management is enabled. Either "Supported" or "N/A".
Requires Inforom PWR object version 3.0 or higher or Kepler device.
InstantaneousPowerDraw
The last measured power draw for the entire board, in watts. Only available if power
management is supported.
AveragePowerDraw
The average power draw for the entire board for the last second, in watts. Only supported
on Ampere (except GA100) or newer devices. Only available if power management is
supported.
PowerLimit The software power limit, in watts. Set by software such as nvidia-smi. Only available if
power management is supported. Requires Inforom PWR object version 3.0 or higher or Kepler
device. On Kepler devices Power Limit can be adjusted using -pl,--power-limit= switches.
EnforcedPowerLimit
The power management algorithm's power ceiling, in watts. Total board power draw is
manipulated by the power management algorithm such that it stays under this value. This
limit is the minimum of various limits such as the software limit listed above. Only
available if power management is supported. Requires a Kepler device. Please note that for
boards without INA sensors, it is the GPU power draw that is being manipulated.
DefaultPowerLimit
The default power management algorithm's power ceiling, in watts. Power Limit will be set
back to Default Power Limit after driver unload. Only on supported devices from Kepler
family.
MinPowerLimit
The minimum value in watts that power limit can be set to. Only on supported devices from
Kepler family.
MaxPowerLimit
The maximum value in watts that power limit can be set to. Only on supported devices from
Kepler family.
PowerSmoothing
Power Smoothing related definitions and currently set values. This feature allows users to tune power
parameters to minimize power fluctuations in large datacenter environments.
Enabled Value is "Yes" if the feature is enabled and "No" if the feature is not enabled.
PrivilegeLevel
The current privilege for the user. Value is 0, 1 or 2. Note that the higher the privilege
level, the more information the user will have access to.
ImmediateRampDown
Values are "Enabled" or "Disabled". Indicates if ramp down hysteresis value will be
honored (when enabled) or ignored (when disabled).
CurrentTMP The last read value of the Total Module Power, in watts.
CurrentTMPFLoor
The last read value of the Total Module Power floor, in watts. This value is calculated by
doing TMP Ceiling * (% TMP FLoor value)
Max%TMPFloor
The highest percentage value for which the Percent TMP Floor can be set.
Min%TMPFloor
The lowest percentage value for which the Percent TMP Floor can be set.
HWLifetime%Remaining
As this feature is used, the circuitry which drives the feature wears down. This value
gives the percentage of the remaining lifetime of this hardware.
NumberofPresetProfiles
This value is the total number of Preset Profiles supported.
CurrentProfile
Values for the currently acvive power smoothing preset profile.
**% TMP Floor**
The percentage of the TMP Ceiling, which is used to set the TMP floor, for the currently
active preset profile. For example, if max TMP is 1000 W, and the % TMP floor is 50%, then
the min TMP value will be 500 W. This value is in the range [Min % TMP Floor, Max % TMP
Floor].
RampUpRate The ramp up rate, measured in mW/s, for the currently active preset profile.
RampDownRate The ramp down rate, measured in mW/s, for the currently active preset profile.
RampDownHysteresis
The ramp down hysteresis value, in ms, for the currently active preset profile.
ActivePresetProfileNumber
The number of the active preset profile.
AdminOverrides
Admin overrides allow users with sufficient permissions to preempt the values of the currently active
preset profile. If an admin override is set for one of the fields, then this value will be used instead
of any other configured value.
**% TMP Floor**
The admin override value for % TMP Floor. This value is in the range [Min % TMP Floor, Max
% TMP Floor].
RampUpRate The admin override value for ramp up rate, measured in mW/s.
RampDownRate The admin override value for ramp down rate, measured in mW/s.
RampDownHysteresis
The admin override value for ramp down hysteresis value, in ms.
WorkloadPowerProfiles
Pre-tuned GPU profiles help to provide immediate, optimized configurations for Datacenter use cases. This
sections includes information about the currently requested on enfornced power profiles.
RequestedProfiles
The list of user requested profiles.
EnforcedProfiles
Since many of the profiles have conflicting goals, some configurations of requested
profiles are incompatible. This is the list of the requested profiles which are currently
enforced.
Clocks
Current frequency at which parts of the GPU are running. All readings are in MHz. Note that it is
possible for clocks to report a lower freqency than the lowest frequency that can be set by SW due to HW
optimizations in certain scenarios.
Graphics Current frequency of graphics (shader) clock.
SM Current frequency of SM (Streaming Multiprocessor) clock.
Memory Current frequency of memory clock.
Video Current frequency of video (encoder + decoder) clocks.
ApplicationsClocks
User specified frequency at which applications will be running at. Can be changed with [-ac \|
--applications-clocks] switches.
Graphics User specified frequency of graphics (shader) clock.
Memory User specified frequency of memory clock.
DefaultApplicationsClocks
Default frequency at which applications will be running at. Application clocks can be changed with [-ac
\| --applications-clocks] switches. Application clocks can be set to default using [-rac \| --reset-
applications-clocks] switches.
Graphics Default frequency of applications graphics (shader) clock.
Memory Default frequency of applications memory clock.
MaxClocks
Maximum frequency at which parts of the GPU are design to run. All readings are in MHz.
On GPUs from Fermi family current P0 clocks (reported in Clocks section) can differ from max clocks by
few MHz.
Graphics Maximum frequency of graphics (shader) clock.
SM Maximum frequency of SM (Streaming Multiprocessor) clock.
Memory Maximum frequency of memory clock.
Video Maximum frequency of video (encoder + decoder) clock.
ClockPolicy
User-specified settings for automated clocking changes such as auto boost.
AutoBoost Indicates whether auto boost mode is currently enabled for this GPU (On) or disabled for
this GPU (Off). Shows (N/A) if boost is not supported. Auto boost allows dynamic GPU
clocking based on power, thermal and utilization. When auto boost is disabled the GPU will
attempt to maintain clocks at precisely the Current Application Clocks settings (whenever
a CUDA context is active). With auto boost enabled the GPU will still attempt to maintain
this floor, but will opportunistically boost to higher clocks when power, thermal and
utilization headroom allow. This setting persists for the life of the CUDA context for
which it was requested. Apps can request a particular mode either via an NVML call (see
NVML SDK) or by setting the CUDA environment variable CUDA_AUTO_BOOST.
AutoBoostDefault
Indicates the default setting for auto boost mode, either enabled (On) or disabled (Off).
Shows (N/A) if boost is not supported. Apps will run in the default mode if they have not
explicitly requested a particular mode. Note: Auto Boost settings can only be modified if
"Persistence Mode" is enabled, which is NOT by default.
Supportedclocks
List of possible memory and graphics clocks combinations that the GPU can operate on (not taking into
account HW brake reduced clocks). These are the only clock combinations that can be passed to
--applications-clocks flag. Supported Clocks are listed only when -q -d SUPPORTED_CLOCKS switches are
provided or in XML format.
Voltage
Current voltage reported by the GPU. All units are in mV.
Graphics Current voltage of the graphics unit. This field is deprecated and always displays "N/A".
Voltage will be removed in a future release.
Fabric
GPU Fabric information
State
Indicates the state of the GPU's handshake with the nvidia-fabricmanager (a.k.a. GPU fabric probe)
Possible values: Completed, In Progress, Not Started, Not supported
Status
Status of the GPU fabric probe response from the nvidia-fabricmanager.
Possible values: NVML_SUCCESS or one of the failure codes.
CliqueID
A clique is a set of GPUs that can communicate to each other over NVLink.
The GPUs belonging to the same clique share the same clique ID.
Clique ID will only be valid for NVLink multi-node systems.
ClusterUUID
UUID of an NVLink multi-node cluster to which this GPU belongs.
Cluster UUID will be zero for NVLink single-node systems.
Health
Bandwidth - is the GPU NVLink bandwidth degraded or not <True/False>
Route Recovery in progress - is NVLink route recovery in progress <True/False>
Route Unhealthy - is NVLink route recovery failed or aborted <True/False>
Access Timeout Recovery - is NVLink access timeout recovery in progress <True/False>
Processes
List of processes having Compute or Graphics Context on the device. Compute processes are reported on all
the fully supported products. Reporting for Graphics processes is limited to the supported products
starting with Kepler architecture.
Each Entry is of format "<GPU Index> <PID> <Type> <Process Name> <GPU Memory Usage>"
GPUIndex Represents NVML Index of the device.
GPUInstanceIndex
Represents GPU Instance Index of the MIG device (if enabled).
ComputeInstanceIndex
Represents Compute Instance Index of the MIG device (if enabled).
PID Represents Process ID corresponding to the active Compute or Graphics context.
Type Displayed as "C" for Compute Process, "G" for Graphics Process, "M" for MPS ("Multi-
Process Service") Compute Process, and "C+G" or "M+C" for the process having both Compute
and Graphics or MPS Compute and Compute contexts.
ProcessName Represents process name for the Compute or Graphics process.
GPUMemoryUsage
Amount of memory used on the device by the context. Not available on Windows when running
in WDDM mode because Windows KMD manages all the memory not NVIDIA driver.
DeviceMonitoring
The "nvidia-smi dmon" command-line is used to monitor one or more GPUs (up to 16 devices) plugged into
the system. This tool allows the user to see one line of monitoring data per monitoring cycle. The output
is in concise format and easy to interpret in interactive mode. The output data per line is limited by
the terminal size. It is supported on Tesla, GRID, Quadro and limited GeForce products for Kepler or
newer GPUs under bare metal 64 bits Linux. By default, the monitoring data includes Power Usage,
Temperature, SM clocks, Memory clocks and Utilization values for SM, Memory, Encoder, Decoder, JPEG and
OFA. It can also be configured to report other metrics such as frame buffer memory usage, bar1 memory
usage, power/thermal violations and aggregate single/double bit ecc errors. If any of the metric is not
supported on the device or any other error in fetching the metric is reported as "-" in the output data.
The user can also configure monitoring frequency and the number of monitoring iterations for each run.
There is also an option to include date and time at each line. All the supported options are exclusive
and can be used together in any order. Note: On MIG-enabled GPUs, querying the utilization of encoder,
decoder, jpeg, ofa, gpu, and memory is not currently supported.
Usage:1)Defaultwithnoargumentsnvidia-smidmon
Monitors default metrics for up to 16 supported devices under natural enumeration (starting with GPU
index 0) at a frequency of 1 sec. Runs until terminated with ^C.
2)Selectoneormoredevicesnvidia-smidmon-i<device1,device2,..,deviceN>
Reports default metrics for the devices selected by comma separated device list. The tool picks up to 16
supported devices from the list under natural enumeration (starting with GPU index 0).
3)Selectmetricstobedisplayednvidia-smidmon-s<metric_group>
<metric_group> can be one or more from the following:
p - Power Usage (in Watts) and GPU/Memory Temperature (in C) if supported
u - Utilization (SM, Memory, Encoder, Decoder, JPEG and OFA Utilization in %)
c - Proc and Mem Clocks (in MHz)
v - Power Violations (in %) and Thermal Violations (as a boolean flag)
m - Frame Buffer, Bar1 and Confidential Compute protected memory usage (in MB)
e - ECC (Number of aggregated single bit, double bit ecc errors) and PCIe Replay errors
t - PCIe Rx and Tx Throughput in MB/s (Maxwell and above)
4)Configuremonitoringiterationsnvidia-smidmon-c<numberofsamples>
Displays data for specified number of samples and exit.
5)Configuremonitoringfrequencynvidia-smidmon-d<timeinsecs>
Collects and displays data at every specified monitoring interval until terminated with ^C.
6)Displaydatenvidia-smidmon-oD
Prepends monitoring data with date in YYYYMMDD format.
7)Displaytimenvidia-smidmon-oT
Prepends monitoring data with time in HH:MM:SS format.
8)SelectGPMmetricstobedisplayednvidia-smidmon--gpm-metrics<gpmMetric1,gpmMetric2,...,gpmMetricN>
<gpmMetricX> Refer to the documentation for nvmlGpmMetricId_t in the NVML header file
9)SelectwhichlevelofGPMmetricstobedisplayednvidia-smidmon--gpm-options<gpmMode>
<gpmMode> can be one of the following:
d - Display Device Level GPM metrics
m - Display MIG Level GPM metrics
dm - Display Device and MIG Level GPM metrics
md - Display Device and MIG Level GPM metrics, same as 'dm'
10)Modifyoutputformatnvidia-smidmon--format<formatSpecifier>
<formatSpecifier> can be any comma separated combination of the following:
csv - Format dmon output as CSV
nounit - Remove unit line from dmon output
noheader - Remove header line from dmon output
11)HelpInformationnvidia-smidmon-h
Displays help information for using the command line.
Daemon(EXPERIMENTAL)
The "nvidia-smi daemon" starts a background process to monitor one or more GPUs plugged in to the system.
It monitors the requested GPUs every monitoring cycle and logs the file in compressed format at the user
provided path or the default location at /var/log/nvstats/. The log file is created with system's date
appended to it and of the format nvstats-YYYYMMDD. The flush operation to the log file is done every
alternate monitoring cycle. Daemon also logs it's own PID at /var/run/nvsmi.pid. By default, the
monitoring data to persist includes Power Usage, Temperature, SM clocks, Memory clocks and Utilization
values for SM, Memory, Encoder, Decoder, JPEG and OFA. The daemon tools can also be configured to record
other metrics such as frame buffer memory usage, bar1 memory usage, power/thermal violations and
aggregate single/double bit ecc errors.The default monitoring cycle is set to 10 secs and can be
configured via command-line. It is supported on Tesla, GRID, Quadro and GeForce products for Kepler or
newer GPUs under bare metal 64 bits Linux. The daemon requires root privileges to run, and only supports
running a single instance on the system. All of the supported options are exclusive and can be used
together in any order. Note: On MIG-enabled GPUs, querying the utilization of encoder, decoder, jpeg,
ofa, gpu, and memory is not currently supported. Usage:1)Defaultwithnoargumentsnvidia-smidaemon
Runs in the background to monitor default metrics for up to 16 supported devices under natural
enumeration (starting with GPU index 0) at a frequency of 10 sec. The date stamped log file is created at
/var/log/nvstats/.
2)Selectoneormoredevicesnvidia-smidaemon-i<device1,device2,..,deviceN>
Runs in the background to monitor default metrics for the devices selected by comma separated device
list. The tool picks up to 16 supported devices from the list under natural enumeration (starting with
GPU index 0).
3)Selectmetricstobemonitorednvidia-smidaemon-s<metric_group>
<metric_group> can be one or more from the following:
p - Power Usage (in Watts) and GPU/Memory Temperature (in C) if supported
u - Utilization (SM, Memory, Encoder, Decoder, JPEG and OFA Utilization in %)
c - Proc and Mem Clocks (in MHz)
v - Power Violations (in %) and Thermal Violations (as a boolean flag)
m - Frame Buffer, Bar1 and Confidential Compute protected memory usage (in MB)
e - ECC (Number of aggregated single bit, double bit ecc errors) and PCIe Replay errors
t - PCIe Rx and Tx Throughput in MB/s (Maxwell and above)
4)Configuremonitoringfrequencynvidia-smidaemon-d<timeinsecs>
Collects data at every specified monitoring interval until terminated.
5)Configurelogdirectorynvidia-smidaemon-p<pathofdirectory>
The log files are created at the specified directory.
6)Configurelogfilenamenvidia-smidaemon-j<stringtoappendlogfilename>
The command-line is used to append the log file name with the user provided string.
7)Terminatethedaemonnvidia-smidaemon-t
This command-line uses the stored PID (at /var/run/nvsmi.pid) to terminate the daemon. It makes the best
effort to stop the daemon and offers no guarantees for it's termination. In case the daemon is not
terminated, then the user can manually terminate by sending kill signal to the daemon. Performing a GPU
reset operation (via nvidia-smi) requires all GPU processes to be exited, including the daemon. Users who
have the daemon open will see an error to the effect that the GPU is busy.
8)HelpInformationnvidia-smidaemon-h
Displays help information for using the command line.
ReplayMode(EXPERIMENTAL)
The "nvidia-smi replay" command-line is used to extract/replay all or parts of log file generated by the
daemon. By default, the tool tries to pull the metrics such as Power Usage, Temperature, SM clocks,
Memory clocks and Utilization values for SM, Memory, Encoder, Decoder, JPEG and OFA. The replay tool can
also fetch other metrics such as frame buffer memory usage, bar1 memory usage, power/thermal violations
and aggregate single/double bit ecc errors. There is an option to select a set of metrics to replay, If
any of the requested metric is not maintained or logged as not-supported then it's shown as "-" in the
output. The format of data produced by this mode is such that the user is running the device monitoring
utility interactively. The command line requires mandatory option "-f" to specify complete path of the
log filename, all the other supported options are exclusive and can be used together in any order. Note:
On MIG-enabled GPUs, querying the utilization of encoder, decoder, jpeg, ofa, gpu, and memory is not
currently supported. Usage:1)Specifylogfiletobereplayednvidia-smireplay-f<logfilename>
Fetches monitoring data from the compressed log file and allows the user to see one line of monitoring
data (default metrics with time-stamp) for each monitoring iteration stored in the log file. A new line
of monitoring data is replayed every other second irrespective of the actual monitoring frequency
maintained at the time of collection. It is displayed till the end of file or until terminated by ^C.
2)Filtermetricstobereplayednvidia-smireplay-f<pathtologfile>-s<metric_group>
<metric_group> can be one or more from the following:
p - Power Usage (in Watts) and GPU/Memory Temperature (in C) if supported
u - Utilization (SM, Memory, Encoder, Decoder, JPEG and OFA Utilization in %)
c - Proc and Mem Clocks (in MHz)
v - Power Violations (in %) and Thermal Violations (as a boolean flag)
m - Frame Buffer, Bar1 and Confidential Compute protected memory usage (in MB)
e - ECC (Number of aggregated single bit, double bit ecc errors) and PCIe Replay errors
t - PCIe Rx and Tx Throughput in MB/s (Maxwell and above)
3)Limitreplaytooneormoredevicesnvidia-smireplay-f<logfile>-i<device1,device2,..,deviceN>
Limits reporting of the metrics to the set of devices selected by comma separated device list. The tool
skips any of the devices not maintained in the log file.
4)Restrictthetimeframebetweenwhichdataisreportednvidia-smireplay-f<logfile>-b<starttimeinHH:MM:SSformat>-e<endtimeinHH:MM:SSformat>
This option allows the data to be limited between the specified time range. Specifying time as 0 with -b
or -e option implies start or end file respectively.
5)Redirectreplayinformationtoalogfilenvidia-smireplay-f<logfile>-r<outputfilename>
This option takes log file as an input and extracts the information related to default metrics in the
specified output file.
6)HelpInformationnvidia-smireplay-h
Displays help information for using the command line.
ProcessMonitoring
The "nvidia-smi pmon" command-line is used to monitor compute and graphics processes running on one or
more GPUs (up to 16 devices) plugged into the system. This tool allows the user to see the statistics for
all the running processes on each device at every monitoring cycle. The output is in concise format and
easy to interpret in interactive mode. The output data per line is limited by the terminal size. It is
supported on Tesla, GRID, Quadro and limited GeForce products for Kepler or newer GPUs under bare metal
64 bits Linux. By default, the monitoring data for each process includes the pid, command name and
average utilization values for SM, Memory, Encoder and Decoder since the last monitoring cycle. It can
also be configured to report frame buffer memory usage for each process. If there is no process running
for the device, then all the metrics are reported as "-" for the device. If any of the metric is not
supported on the device or any other error in fetching the metric is also reported as "-" in the output
data. The user can also configure monitoring frequency and the number of monitoring iterations for each
run. There is also an option to include date and time at each line. All the supported options are
exclusive and can be used together in any order. Note: On MIG-enabled GPUs, querying the utilization of
encoder, decoder, jpeg, ofa, gpu, and memory is not currently supported.
Usage:1)Defaultwithnoargumentsnvidia-smipmon
Monitors all the processes running on each device for up to 16 supported devices under natural
enumeration (starting with GPU index 0) at a frequency of 1 sec. Runs until terminated with ^C.
2)Selectoneormoredevicesnvidia-smipmon-i<device1,device2,..,deviceN>
Reports statistics for all the processes running on the devices selected by comma separated device list.
The tool picks up to 16 supported devices from the list under natural enumeration (starting with GPU
index 0).
3)Selectmetricstobedisplayednvidia-smipmon-s<metric_group>
<metric_group> can be one or more from the following:
u - Utilization (SM, Memory, Encoder, Decoder, JPEG, and OFA Utilization for the process in %). Reports
average utilization since last monitoring cycle.
m - Frame Buffer and Confidential Compute protected memory usage (in MB). Reports instantaneous value for
memory usage.
4)Configuremonitoringiterationsnvidia-smipmon-c<numberofsamples>
Displays data for specified number of samples and exit.
5)Configuremonitoringfrequencynvidia-smipmon-d<timeinsecs>
Collects and displays data at every specified monitoring interval until terminated with ^C. The
monitoring frequency must be between 1 to 10 secs.
6)Displaydatenvidia-smipmon-oD
Prepends monitoring data with date in YYYYMMDD format.
7)Displaytimenvidia-smipmon-oT
Prepends monitoring data with time in HH:MM:SS format.
8)HelpInformationnvidia-smipmon-h
Displays help information for using the command line.
Topology
List topology information about the system's GPUs, how they connect to each other, their CPU and memory
affinities as well as qualified NICs capable of RDMA.
Note: On some systems, a NIC is used as a PCI bridge for the NVLINK switches and is not useful from a
networking or RDMA point of view. The nvidia-smi topo command will filter the NIC's ports/PCIe sub-
functions out of the topology matrix by examining the NIC's sysfs entries. On some kernel versions,
nvidia-smi requires root privileges to read these sysfs entries.
Usage:TopologyconnectionsandaffinitiesmatrixbetweentheGPUsandNICsinthesystemnvidia-smitopo-m
Displays a matrix of connections between all GPUs and NICs in the system along with CPU/memory affinities
for the GPUs with the following legend:
Legend:
X = Self
SYS = Connection traversing PCIe as well as the SMP interconnect between NUMA nodes (e.g., QPI/UPI)
NODE = Connection traversing PCIe as well as the interconnect between PCIe Host Bridges within a NUMA
node
PHB = Connection traversing PCIe as well as a PCIe Host Bridge (typically the CPU)
PXB = Connection traversing multiple PCIe switches (without traversing the PCIe Host Bridge)
PIX = Connection traversing a single PCIe switch NV# = Connection traversing a bonded set of # NVLinks
Note: This command may also display bonded NICs which may not be RDMA capable.
nvidia-smitopo-mp
Displays a matrix of PCI-only connections between all GPUs and NICs in the system along with CPU/memory
affinities for the GPUs with the same legend as the 'nvidia-smi topo -m' command. This command excludes
NVLINK connections and shows PCI connections between GPUs.
nvidia-smitopo-c<CPUnumber>
Shows all the GPUs with an affinity to the specified CPU number.
nvidia-smitopo-n<traversal_path>-i<deviceID>
Shows all the GPUs connected with the given GPU using the specified traversal path. The traversal path
values are:
0 = A single PCIe switch on a dual GPU board
1 = A single PCIe switch
2 = Multiple PCIe switches
3 = A PCIe host bridge
4 = An on-CPU interconnect link between PCIe host bridges
5 = An SMP interconnect link between NUMA nodes
nvidia-smitopo-p-i<deviceID1>,<deviceID2>
Shows the most direct PCIe path traversal for a given pair of GPUs.
nvidia-smitopo-p2p<capability>
Shows the P2P status between all GPUs, given a capability. Capability values are:
r - p2p read capability
w - p2p write capability
n - p2p nvlink capability
a - p2p atomics capability
p - p2p pcie capability
nvidia-smitopo-C-i<deviceID>
Shows the NUMA ID of the nearest CPU for a GPU represented by the device ID.
nvidia-smitopo-M-i<deviceID>
Shows the NUMA ID of the nearest memory for a GPU represented by the device ID.
nvidia-smitopo-gnid-i<deviceID>
Shows the NUMA ID of the GPU represented by the device ID, if applicable. Displays N/A otherwise.
nvidia-smitopo-nvme
Displays a matrix of PCI connections between all GPUs and NVME devices in the system with the following
legend:
Legend:
X = Self
SYS = Connection traversing PCIe as well as the SMP interconnect between NUMA nodes (e.g., QPI/UPI)
NODE = Connection traversing PCIe as well as the interconnect between PCIe Host Bridges within a NUMA
node
PHB = Connection traversing PCIe as well as a PCIe Host Bridge (typically the CPU)
PXB = Connection traversing multiple PCIe bridges (without traversing the PCIe Host Bridge)
PIX = Connection traversing at most a single PCIe bridge
Nvlink
The "nvidia-smi nvlink" command-line is used to manage the GPU's Nvlinks. It provides options to set and
query Nvlink information.
Usage:1)Displayhelpmenunvidia-sminvlink-h
Displays help menu for using the command-line.
2)ListoneormoreGPUsnvidia-sminvlink-i<GPUIDs>nvidia-sminvlink--id<GPUIDs>
Selects one or more GPUs using the given comma-separated GPU indexes, PCI bus IDs or UUIDs. If not used,
the given command-line option applies to all of the supported GPUs.
3)SelectaspecificNvLinknvidia-sminvlink-l<GPUNvlinkId>nvidia-sminvlink--list<GPUNvlinkId>
Selects a specific Nvlink of the GPU for the given command, if valid. If not used, the given command-line
option allies to all of the GPU's Nvlinks.
4)QueryNvlinkStatusnvidia-sminvlink-snvidia-sminvlink--status
Get the status of the GPU's Nvlinks.
If Active, the Bandwidth of the links will be displayed.
If the link is present but Not Active, it will show the link as Inactive.
If the link is in Sleep state, it will show as Sleep.
5)QueryNvlinkcapabilitiesnvidia-sminvlink-cnvidia-sminvlink--capabilities
Get the GPU's Nvlink capabilities.
6)QuerytheNvlink'sremotenodePCIbusnvidia-sminvlink-pnvidia-sminvlink-pcibusid
Get the Nvlink's remote node PCI bus ID.
7)QuerytheNvlink'sremotelinkinfonvidia-sminvlink-Rnvidia-sminvlink-remotelinkinfo
Get the remote device PCI bus ID and NvLink ID for a link.
8)SetNvlinkCounterControlisDEPRECATED9)GetNvlinkCounterControlisDEPRECATED10)GetNvlinkCountersisDEPRECATED,-gt/--getthroughputshouldbeusedinstead11)ResetNvlinkcountersisDEPRECATED12)QueryNvlinkErrorCountersnvidia-sminvlink-envidia-sminvlink--errorcounters
Get the Nvlink error counters.
For NVLink 4
Replay Errors - count the number of replay 'events' that occurred
Recovery Errors - count the number of link recovery events
CRC Errors - count the number of CRC errors in received packets
For NVLink 5
Tx packets - Total Tx packets on the link
Tx bytes - Total Tx bytes on the link
Rx packets - Total Rx packets on the link
Rx bytes - Total Rx bytes on the link
Malformed packet Errors - Number of packets Rx on a link where packets are malformed
Buffer overrun Errors - Number of packets that were discarded on Rx due to buffer overrun
Rx Errors - Total number of packets with errors Rx on a link
Rx remote Errors - Total number of packets Rx - stomp/EBP marker
Rx General Errors - Total number of packets Rx with header mismatch
Local link integrity Errors - Total number of times that the count of local errors exceeded a threshold
Tx discards - Total number of tx error packets that were discarded
Link recovery successful events - Number of times link went from Up to recovery, succeeded and link came
back up
Link recovery failed events - Number of times link went from Up to recovery, failed and link was declared
down
Total link recovery events - Number of times link went from Up to recovery, irrespective of the result
Effective Errors - Sum of the number of errors in each Nvlink packet
Effective BER - BER for symbol errors
Symbol Errors - Number of errors in rx symbols
Symbol BER - BER for symbol errors
FEC Errors - [0-15] - count of symbol errors that are corrected
13)QueryNvlinkCRCerrorcountersnvidia-sminvlink-ecnvidia-sminvlink--crcerrorcounters
Get the Nvlink per-lane CRC/ECC error counters.
CRC - NVLink 4 and before - Total Rx CRC errors on an NVLink Lane
ECC - NVLink 4 - Total Rx ECC errors on an NVLink Lane
Deprecated NVLink 5 onwards
14)ResetNvlinkErrorCountersnvidia-sminvlink-renvidia-sminvlink--reseterrorcounters
Reset all Nvlink error counters to zero.
NvLink 5 NOT SUPPORTED
15)QueryNvlinkthroughputcountersnvidia-sminvlink-gt<DataType>nvidia-sminvlink--getthroughput<DataType>
<Data Type> can be one of the following:
d - Tx and Rx data payload in KiB.
r - Tx and Rx raw payload and protocol overhead in KiB.
16)SetNvlinkLowPowerthresholdsnvidia-sminvlink-sLowPwrThres<Threshold>nvidia-sminvlink--setLowPowerThreshold<Threshold>
Set the Nvlink Low Power Threshold, before the links go into Low Power Mode.
Threshold ranges and units can be found using -gLowPwrInfo.
17)GetNvlinkLowPowerInfonvidia-sminvlink-gLowPwrInfonvidia-sminvlink--getLowPowerInfo
Query the Nvlink's Low Power Info.
18)SetNvlinkBandwidthmodenvidia-sminvlink-sBwMode<BandwidthMode>nvidia-sminvlink--setBandwidthMode<BandwidthMode>
Set the Nvlink Bandwidth mode for all GPUs. This is DEPRECATED for Blackwell+.
The options are:
FULL - All links are at max Bandwidth.
OFF - Bandwidth is not used. P2P is via PCIe bus.
MIN - Bandwidth is at minimum speed.
HALF - Bandwidth is at around half of FULL speed.
3QUARTER - Bandwidth is at around 75% of FULL speed.
19)GetNvlinkBandwidthmodenvidia-sminvlink-gBwModenvidia-sminvlink--getBandwidthMode
Get the Nvlink Bandwidth mode for all GPUs. THis is DEPRECATED for Blackwell+.
20)QueryforNvlinkBridgenvidia-sminvlink-cBridgenvidia-sminvlink--checkBridge
Query for Nvlink Bridge presence.
21)SettheGPU'sNvlinkWidthnvidia-sminvlink-sLWidth<LinkWidth>nvidia-sminvlink--setLinkWidth<LinkWidth>
Set the GPU's Nvlink width, which will be keep those number of links Active, and the rest to sleep.
<Link Width> can be one of the following:
values - List possible Link Widths to be set.
The numerical value from the above option.
22)GettheGPU'sNvlinkWidthnvidia-sminvlink-gLWidthnvidia-sminvlink--getLinkWidth
Query the GPU's Nvlink Width.
C2C
The "nvidia-smi c2c" command-line is used to manage the GPU's C2C Links. It provides options to query C2C
Link information.
Usage:1)Displayhelpmenunvidia-smic2c-h
Displays help menu for using the command-line.
2)ListoneormoreGPUsnvidia-smic2c-i<GPUIDs>nvidia-smic2c--id<GPUIDs>
Selects one or more GPUs using the given comma-separated GPU indexes, PCI bus IDs or UUIDs. If not used,
the given command-line option applies to all of the supported GPUs.
3)SelectaspecificC2CLinknvidia-smic2c-l<GPUC2CId>nvidia-smic2c--list<GPUC2CId>
Selects a specific C2C Link of the GPU for the given command, if valid. If not used, the given command-
line option allies to all of the GPU's C2C Links.
4)QueryC2CLinkStatusnvidia-smic2c-snvidia-smic2c--status
Get the status of the GPU's C2C Links. If active, the Bandwidth of the links will be displayed.
5)QueryC2CLinkErrorCountersnvidia-smic2c-envidia-smic2c-errorCounters
Display the C2C Link error counters.
6)QueryC2CLinkPowerInfonvidia-smic2c-gLowPwrInfonvidia-smic2c-getLowPowerInfo
Display the C2C Link Power state.
>
vGPUManagement
The "nvidia-smi vgpu" command reports on GRID vGPUs executing on supported GPUs and hypervisors (refer to
driver release notes for supported platforms). Summary reporting provides basic information about vGPUs
currently executing on the system. Additional options provide detailed reporting of vGPU properties, per-
vGPU reporting of SM, Memory, Encoder, Decoder, Jpeg, and OFA utilization, and per-GPU reporting of
supported and creatable vGPUs. Periodic reports can be automatically generated by specifying a
configurable loop frequency to any command. Note: On MIG-enabled GPUs, querying the utilization of
encoder, decoder, jpeg, ofa, gpu, and memory is not currently supported.
Usage:1)HelpInformationnvidia-smivgpu-h
Displays help information for using the command line.
2)Defaultwithnoargumentsnvidia-smivgpu
Reports summary of all the vGPUs currently active on each device.
3)DisplaydetailedinfooncurrentlyactivevGPUsnvidia-smivgpu-q
Collects and displays information on currently active vGPUs on each device, including driver version,
utilization, and other information.
4)Selectoneormoredevicesnvidia-smivgpu-i<device1,device2,..,deviceN>
Reports summary for all the vGPUs currently active on the devices selected by comma-separated device
list.
5)DisplaysupportedvGPUsnvidia-smivgpu-s
Displays vGPU types supported on each device. Use the -v / --verbose option to show detailed info on each
vGPU type.
6)DisplaycreatablevGPUsnvidia-smivgpu-c
Displays vGPU types creatable on each device. This varies dynamically, depending on the vGPUs already
active on the device. Use the -v / --verbose option to show detailed info on each vGPU type.
7)ReportutilizationforcurrentlyactivevGPUs.nvidia-smivgpu-u
Reports average utilization (SM, Memory, Encoder, Decoder, Jpeg, and OFA) for each active vGPU since last
monitoring cycle. The default cycle time is 1 second, and the command runs until terminated with ^C. If a
device has no active vGPUs, its metrics are reported as "-".
8)Configureloopfrequencynvidia-smivgpu[-s-c-q-u]-l<timeinsecs>
Collects and displays data at a specified loop interval until terminated with ^C. The loop frequency must
be between 1 and 10 secs. When no time is specified, the loop frequency defaults to 5 secs.
9)DisplayGPUengineusagenvidia-smivgpu-p
Display GPU engine usage of currently active processes running in the vGPU VMs.
10)Displaymigrationcapabitlities.nvidia-smivgpu-m
Display pGPU's migration/suspend/resume capability.
11)DisplaythevGPUSoftwareschedulerstate.nvidia-smivgpu-ss
Display the information about vGPU Software scheduler state.
12)DisplaythevGPUSoftwareschedulercapabilities.nvidia-smivgpu-sc
Display the list of supported vGPU scheduler policies returned along with the other capabilities values,
if the engine is Graphics type. For other engine types, it is BEST EFFORT policy and other capabilities
will be zero. If ARR is supported and enabled, scheduling frequency and averaging factor are applicable
else timeSlice is applicable.
13)DisplaythevGPUSoftwareschedulerlogs.nvidia-smivgpu-sl
Display the vGPU Software scheduler runlist logs.
nvidia-smi--query-vgpu-scheduler-logs=[inputparameters]
Display the vGPU Software scheduler runlist logs in CSV format.
14)SetthevGPUSoftwareschedulerstate.nvidia-smivgpu--set-vgpu-scheduler-state[options]
Set the vGPU Software scheduler policy and states.
15)DisplayNvidiaEncodersessioninfo.nvidia-smivgpu-es
Display the information about encoder sessions for currently running vGPUs.
16)Displayaccountingstatistics.nvidia-smivgpu--query-accounted-apps=[inputparameters]
Display accounting stats for compute/graphics processes.
To find the list of properties which can be queried, run - 'nvidia-smi --help-query-accounted-apps'.
17)DisplayNvidiaFrameBufferCapturesessioninfo.nvidia-smivgpu-fs
Display the information about FBC sessions for currently running vGPUs.
Note:Horizontalresolution,verticalresolution,averageFPSandaveragelatencydataforaFBCsessionmaybezeroiftherearenonewframescapturedsincethesessionstarted.18)SetvGPUheterogeneousmode.nvidia-smivgpu-shm
Set vGPU heterogeneous mode of the device for timesliced vGPUs with different framebuffer sizes.
>
19)SetvGPUMIGtimeslicemode.
>
nvidia-smivgpu-smts
Set vGPU MIG timeslice mode of the device.
>
20)DisplaythecurrentlycreatablevGPUtypesontheuserprovidedGPUInstancenvidia-smivgpu-c-gi<GPUinstanceIDs>-i<GPUIDs>
>
nvidia-smivgpu-c--gpu-instance-id<GPUinstanceIDs>--id<GPUIDs>
>
Provide comma separated values for more than one GPU instance. The target GPU index (MANDATORY) for the
given GPU instance.
21)DisplaydetailedinformationofthecurrentlyactivevGPUinstancesontheuserprovidedGPUInstancenvidia-smivgpu-q-gi<GPUinstanceIDs>-i<GPUIDs>
>
nvidia-smivgpu-q--gpu-instance-id<GPUinstanceIDs>--id<GPUIDs>
>
Provide comma separated values for more than one GPU instance. The target GPU index (MANDATORY) for the
given GPU instance.
22)DisplaythevGPUschedulerstateontheuserprovidedGPUInstance
>
nvidia-smivgpu-ss-gi<GPUinstanceIDs>-i<GPUIDs>
>
nvidia-smivgpu-ss--gpu-instance-id<GPUinstanceIDs>--id<GPUIDs>
>
Provide comma separated values for more than one GPU instance. The target GPU index (MANDATORY) for the
given GPU instance.
23)GetthevGPUheterogeneousmodeontheuserprovidedGPUInstance
>
nvidia-smivgpu-ghm-gi<GPUinstanceIDs>-i<GPUIDs>
>
nvidia-smivgpu-ghm--gpu-instance-id<GPUinstanceIDs>--id<GPUIDs>
>
Provide comma separated values for more than one GPU instance. The target GPU index (MANDATORY) for the
given GPU instance. If not used, the given command-line option applies to all of the GPU instances.
24)SetthevGPUheterogeneousmodeontheuserprovidedGPUInstance
>
nvidia-smivgpu-shm-gi<GPUinstanceIDs>-i<GPUIDs>
>
nvidia-smivgpu-shm--gpu-instance-id<GPUinstanceIDs>--id<GPUIDs>
>
Provide comma separated values for more than one GPU instance. The target GPU index (MANDATORY) for the
given GPU instance.
25)SetthevGPUSoftwareschedulerstateontheuserprovidedGPUInstance.nvidia-smivgpuset-vgpu-scheduler-state[options]-gi<GPUinstanceIDs>-i<GPUIDs>nvidia-smivgpuset-vgpu-scheduler-state[options]--gpu-instance-id<GPUinstanceIDs>--id<GPUIDs>
>
Provide comma separated values for more than one GPU instance. The target GPU index (MANDATORY) for the
given GPU instance.
26)DisplaythevGPUschedulerlogsontheuserprovidedGPUInstance
>
nvidia-smivgpu-sl-gi<GPUinstanceIDs>-i<GPUIDs>
>
nvidia-smivgpu-sl--gpu-instance-id<GPUinstanceIDs>--id<GPUIDs>
>
Provide comma separated values for more than one GPU instance. The target GPU index (MANDATORY) for the
given GPU instance.
>
nvidia-smivgpu--query-gpu-instance-vgpu-scheduler-logs=[inputparameters]-gi<GPUinstanceIDs>-i<GPUIDs>
>
Display the vGPU Software scheduler logs in CSV format on the user provided GPU Instance.
27)DisplaydetailedinformationofthecurrentlycreatablevGPUtypesontheuserprovidedGPUInstancenvidia-smivgpu-c-v-gi<GPUinstanceIDs>-i<GPUIDs>
>
nvidia-smivgpu-c-v--gpu-instance-id<GPUinstanceIDs>--id<GPUIDs>
>
Provide comma separated values for more than one GPU instance. The target GPU index (MANDATORY) for the
given GPU instance.
MIGManagement
The privileged "nvidia-smi mig" command-line is used to manage MIG-enabled GPUs. It provides options to
create, list and destroy GPU instances and compute instances.
Usage:1)Displayhelpmenunvidia-smimig-h
Displays help menu for using the command-line.
2)SelectoneormoreGPUsnvidia-smimig-i<GPUIDs>nvidia-smimig--id<GPUIDs>
Selects one or more GPUs using the given comma-separated GPU indexes, PCI bus IDs or UUIDs. If not used,
the given command-line option applies to all of the supported GPUs.
3)SelectoneormoreGPUinstancesnvidia-smimig-gi<GPUinstanceIDs>nvidia-smimig--gpu-instance-id<GPUinstanceIDs>
Selects one or more GPU instances using the given comma-separated GPU instance IDs. If not used, the
given command-line option applies to all of the GPU instances.
4)Selectoneormorecomputeinstancesnvidia-smimig-ci<computeinstanceIDs>nvidia-smimig--compute-instance-id<computeinstanceIDs>
Selects one or more compute instances using the given comma-separated compute instance IDs. If not used,
the given command-line option applies to all of the compute instances.
5)ListGPUinstanceprofilesnvidia-smimig-lgip-i<GPUIDs>nvidia-smimig--list-gpu-instance-profiles--id<GPUIDs>
Lists GPU instance profiles, their availability and IDs. Profiles describe the supported types of GPU
instances, including all of the GPU resources they exclusively control.
6)ListGPUinstancepossibleplacementsnvidia-smimig-lgipp-i<GPUIDs>nvidia-smimig--list-gpu-instance-possible-placements--id<GPUIDs>
Lists GPU instance possible placements. Possible placements describe the locations of the supported types
of GPU instances within the GPU.
7)CreateGPUinstancenvidia-smimig-cgi<GPUinstancespecifiers>-i<GPUIDs>nvidia-smimig--create-gpu-instance<GPUinstancespecifiers>--id<GPUIDs>
Creates GPU instances for the given GPU instance specifiers. A GPU instance specifier comprises a GPU
instance profile name or ID and an optional placement specifier consisting of a colon and a placement
start index. The command fails if the GPU resources required to allocate the requested GPU instances are
not available, or if the placement index is not valid for the given profile.
8)CreateaGPUinstancealongwiththedefaultcomputeinstancenvidia-smimig-cgi<GPUinstanceprofileIDsornames>-i<GPUIDs>-Cnvidia-smimig--create-gpu-instance<GPUinstanceprofileIDsornames>--id<GPUIDs>--default-compute-instance9)ListGPUinstancesnvidia-smimig-lgi-i<GPUIDs>nvidia-smimig--list-gpu-instances--id<GPUIDs>
Lists GPU instances and their IDs.
10)DestroyGPUinstancenvidia-smimig-dgi-gi<GPUinstanceIDs>-i<GPUIDs>nvidia-smimig--destroy-gpu-instances--gpu-instance-id<GPUinstanceIDs>--id<GPUIDs>
Destroys GPU instances. The command fails if the requested GPU instance is in use by an application.
11)Listcomputeinstanceprofilesnvidia-smimig-lcip-gi<GPUinstanceIDs>-i<GPUIDs>nvidia-smimig--list-compute-instance-profiles--gpu-instance-id<GPUinstanceIDs>--id<GPUIDs>
Lists compute instance profiles, their availability and IDs. Profiles describe the supported types of
compute instances, including all of the GPU resources they share or exclusively control.
12)Listcomputeinstancepossibleplacementsnvidia-smimig-lcipp-gi<GPUinstanceIDs>-i<GPUIDs>nvidia-smimig--list-compute-instance-possible-placements--gpu-instance-id<GPUinstanceIDs>--id<GPUIDs>
Lists compute instance possible placements. Possible placements describe the locations of the supported
types of compute instances within the GPU instance.
13)Createcomputeinstancenvidia-smimig-cci<computeinstanceprofileIDsornames>-gi<GPUinstanceIDs>-i<GPUIDs>nvidia-smimig--create-compute-instance<computeinstanceprofileIDsornames>--gpu-instance-id<GPUinstanceIDs>--id<GPUIDs>
Creates compute instances for the given compute instance spcifiers. A compute instance specifier
comprises a compute instance profile name or ID and an optional placement specifier consisting of a colon
and a placement start index. The command fails if the GPU resources required to allocate the requested
compute instances are not available, or if the placement index is not valid for the given profile.
14)Listcomputeinstancesnvidia-smimig-lci-gi<GPUinstanceIDs>-i<GPUIDs>nvidia-smimig--list-compute-instances--gpu-instance-id<GPUinstanceIDs>--id<GPUIDs>
Lists compute instances and their IDs.
15)Destroycomputeinstancenvidia-smimig-dci-ci<computeinstanceIDs>-gi<GPUinstanceIDs>-i<GPUIDs>nvidia-smimig--destroy-compute-instance--compute-instance-id<computeinstanceIDs>--gpu-instance-id<GPUinstanceIDs>--id<GPUIDs>
Destroys compute instances. The command fails if the requested compute instance is in use by an
application.
BoostSlider
The privileged "nvidia-smi boost-slider" command-line is used to manage boost slider on GPUs. It provides
options to list and control boost sliders.
Usage:1)Displayhelpmenunvidia-smiboost-slider-h
Displays help menu for using the command-line.
2)ListoneormoreGPUsnvidia-smiboost-slider-i<GPUIDs>nvidia-smiboost-slider--id<GPUIDs>
Selects one or more GPUs using the given comma-separated GPU indexes, PCI bus IDs or UUIDs. If not used,
the given command-line option applies to all of the supported GPUs.
3)Listboostslidersnvidia-smiboost-slider-lnvidia-smiboost-slider--list
List all boost sliders for the selected devices.
4)Setvideoboostslidernvidia-smiboost-slider--vboost<value>
Set the video boost slider for the selected devices.
PowerHint
The privileged "nvidia-smi power-hint" command-line is used to query power hint on GPUs.
Usage:1)Displayhelpmenunvidia-smiboost-slider-h
Displays help menu for using the command-line.
2)ListoneormoreGPUsnvidia-smiboost-slider-i<GPUIDs>nvidia-smiboost-slider--id<GPUIDs>
Selects one or more GPUs using the given comma-separated GPU indexes, PCI bus IDs or UUIDs. If not used,
the given command-line option applies to all of the supported GPUs.
3)Listpowerhintinfonvidia-smiboost-slider-lnvidia-smiboost-slider--list-info
List all boost sliders for the selected devices.
4)Querypowerhintnvidia-smiboost-slider-gc<value>-t<value>-p<profileID>nvidia-smiboost-slider--graphics-clock<value>--temperature<value>--profile<profileID>
Query power hint with graphics clock, temperature and profile id.
5)Querypowerhintnvidia-smiboost-slider-gc<value>-mc<value>-t<value>-p<profileID>nvidia-smiboost-slider--graphics-clock<value>--memory-clock<value>--temperature<value>--profile<profileID>
Query power hint with graphics clock, memory clock, temperature and profile id.
ConfidentialCompute
The "nvidia-smi conf-compute" command-line is used to manage confidential compute. It provides options to
set and query confidential compute.
Usage:1)Displayhelpmenunvidia-smiconf-compute-h
Displays help menu for using the command-line.
2)ListoneormoreGPUsnvidia-smiconf-compute-i<GPUIDs>nvidia-smiconf-compute--id<GPUIDs>
Selects one or more GPUs using the given comma-separated GPU indexes, PCI bus IDs or UUIDs. If not used,
the given command-line option applies to all of the supported GPUs.
3)QueryconfidentialcomputeCPUcapabilitynvidia-smiconf-compute-gcnvidia-smiconf-compute--get-cpu-caps
Get confidential compute CPU capability.
4)QueryconfidentialcomputeGPUscapabilitynvidia-smiconf-compute-ggnvidia-smiconf-compute--get-gpus-caps
Get confidential compute GPUs capability.
5)Queryconfidentialcomputedevtoolsmodenvidia-smiconf-compute-dnvidia-smiconf-compute--get-devtools-mode
Get confidential compute DevTools mode.
6)Queryconfidentialcomputeenvironmentnvidia-smiconf-compute-envidia-smiconf-compute--get-environment
Get confidential compute environment.
7)Queryconfidentialcomputefeaturestatusnvidia-smiconf-compute-fnvidia-smiconf-compute--get-cc-feature
Get confidential compute CC feature status.
8)QueryconfidentialcomputeGPUprotected/unprotectedmemorysizesnvidia-smiconf-compute-gmnvidia-smiconf-compute--get-mem-size-info
Get confidential compute GPU protected/unprotected memory sizes.
9)SetconfidentialcomputeGPUunprotectedmemorysizenvidia-smiconf-compute-sm<value>nvidia-smiconf-compute--set-unprotected-mem-size<value>
Set confidential compute GPU unprotected memory size in KiB. Requires root.
10)SetconfidentialcomputeGPUsreadystatenvidia-smiconf-compute-srs<value>nvidia-smiconf-compute--set-gpus-ready-state<value>
Set confidential compute GPUs ready state. The value must be 1 to set the ready state and 0 to unset it.
Requires root.
11)QueryconfidentialcomputeGPUsreadystatenvidia-smiconf-compute-grsnvidia-smiconf-compute--get-gpus-ready-state
Get confidential compute GPUs ready state.
12)SetConfidentialComputeKeyRotationMaxAttackerAdvantagenvidia-smiconf-compute-skr<value>nvidia-smiconf-compute--set-key-rotation-max-attacker-advantage
Set Confidential Compute Key Rotation Max Attacker Advantage.
13)DisplayConfidentialComputeKeyRotationThresholdInfonvidia-smiconf-compute-gkrnvidia-smiconf-compute--get-key-rotation-threshold-info
Display Confidential Compute Key Rotation Threshold Info.
14)DisplayConfidentialComputeMulti-GPUModenvidia-smiconf-compute-mgmnvidia-smiconf-compute--get-multigpu-mode
Display Confidential Compute Multi-GPU Mode.
>
15)DisplayConfidentialComputeDetailedInfonvidia-smiconf-compute-qnvidia-smiconf-compute--query-conf-compute
Display Confidential Compute Detailed Info.
>
GPUPerformanceMonitoring(GPM)StreamState
The "nvidia-smi gpm" command-line is used to manage GPU performance monitoring unit. It provides options
to query and set the stream state.
Usage:1)Displayhelpmenunvidia-smigpm-h
Displays help menu for using the command-line.
2)ListoneormoreGPUsnvidia-smigpm-i<GPUIDs>nvidia-smigpm--id<GPUIDs>
Selects one or more GPUs using the given comma-separated GPU indexes, PCI bus IDs or UUIDs. If not used,
the given command-line option applies to all of the supported GPUs.
3)QueryGPUperformancemonitoringstreamstatenvidia-smigpm-gnvidia-smigpm--get-stream-state
Get gpm stream state for the selected devices.
4)SetGPUperformancemonitoringstreamstatenvidia-smigpm-s<value>nvidia-smigpm--set-stream-state<value>
Set gpm stream state for the selected devices.
GPUPCIsection
The "nvidia-smi pci" command-line is used to manage GPU PCI counters. It provides options to query and
clear PCI counters.
Usage:1)Displayhelpmenunvidia-smipci-h
Displays help menu for using the command-line.
2)QueryPCIerrorcountersnvidia-smipci-i<GPUindex>-gErrCnt
Query PCI error counters of a GPU
3)ClearPCIerrorcountersnvidia-smipci-i<GPUindex>-cErrCnt
Clear PCI error counters of a GPU
4)QueryPCIcountersnvidia-smipci-i<GPUindex>-gCnt
Query PCI RX and TX counters of a GPU
PowerSmoothing
The "nvidia-smi power-smoothing" command-line is used to manage Power Smoothing related data on the GPU.
It provides options to set Power Smoothing related data and query the preset profile definitions.
Usage:1)Displayhelpmenunvidia-smipower-smoothing-h
Displays help menu for using the command-line.
2)ListoneormoreGPUsnvidia-smipower-smoothing-i<GPUIDs>nvidia-smipower-smoothing--id<GPUIDs>
Selects one or more GPUs using the given comma-separated GPU indexes, PCI bus IDs or UUIDs. If not used,
the given command-line option applies to all of the supported GPUs.
2)ListonePresetProfileIDnvidia-smipower-smoothing-p<ProfileID>nvidia-smipower-smoothing--profile<ProfileID>
Selects a Preset Profile ID for which to update a value. This is required when updating a Preset Profile
parameter and prohibited in all other cases.
2)SetActivePresetProfileIDnvidia-smipower-smoothing-spp<ProfileID>nvidia-smipower-smoothing--set-preset-profile<ProfileID>
Activate the deisred Preset Profile ID. Requires root.
2)UpdatepercentageTotalModulePower(TMP)floornvidia-smipower-smoothing-ptf<Percentage>-p<ProfileID>nvidia-smipower-smoothing--percent-tmp-floor<Percentage>--profile<ProfileID>
Sets the percentage TMP floor to inputted value for a given Preset Profile ID. The desired percentage
should be from 0 - 100, given in the form of "AB.CD", with a maximum of two decimal places of precision.
For example, to set value to 34.56%, user will input 34.56. Input can also contain zero or one decimal
places of precision. This option requires a profile ID as an argument. Requires root.
2)UpdateRamp-UpRatenvidia-smipower-smoothing-rur<value>-p<ProfileID>nvidia-smipower-smoothing--ramp-up-rate<value>--profile<ProfileID>
Sets the Ramp-Up Rate to the desired value for a given Preset Profile ID. The rate given must be in the
units of mW/s. This option requires a profile ID as an argument. Requires root.
2)UpdateRamp-DownRatenvidia-smipower-smoothing-rdr<value>-p<ProfileID>nvidia-smipower-smoothing--ramp-down-rate<value>--profile<ProfileID>
Sets the Ramp-Down Rate to the desired value for a given Preset Profile ID. The rate given must be in the
units of mW/s. This option requires a profile ID as an argument. Requires root.
2)UpdateRamp-DownHysteresisnvidia-smipower-smoothing-rdh<value>-p<ProfileID>nvidia-smipower-smoothing--ramp-down-hysteresis<value>--profile<ProfileID>
Sets the Ramp-Down Hysteresis to the desired value for a given Preset Profile ID. The rate given must be
in the units of ms. This option requires a profile ID as an argument. Requires root.
2)DisplaysthePresetProfiledefinitionsforallProfileIDsnvidia-smipower-smoothing-ppdnvidia-smipower-smoothing--print-profile-definitions
Displays all values for each Preset Profile IDs.
2)SetFeatureStatenvidia-smipower-smoothing-s<state>nvidia-smipower-smoothing--state<state>
Sets the state of the feature to either 0/DISABLED or 1/ENABLED. Requires root.
PowerProfiles"
The "nvidia-smi power-profiles" command-line is used to manage Workload Power Profiles related data on
the GPU. It provides options to update Power Profiles data and query the supported Power Profiles.
Usage:1)Displayhelpmenunvidia-smipower-profiles-h
Displays help menu for using the command-line.
2)ListoneormoreGPUsnvidia-smipower-profiles-i<GPUIDs>nvidia-smipower-profiles--id<GPUIDs>
Selects one or more GPUs using the given comma-separated GPU indexes, PCI bus IDs or UUIDs. If not used,
the given command-line option applies to all of the supported GPUs.
3)ListPowerProfilesnvidia-smipower-profiles-lnvidia-smipower-profiles--list
List all Workload Power Profiles supported by the device.
4)ListDetailedPowerProfilesinfonvidia-smipower-profiles-ldnvidia-smipower-profiles--list-detailed
List all Workload Power Profiles supported by the device along with their metadata. This includes the
Profile ID, the Priority (where a lower number indicates a higher priority), and Profiles that conflict
with the given profile. If two or more conflicting profiles are requested, not all my be enforced.
5)GetRequestedProfilesnvidia-smipower-profiles-grnvidia-smipower-profiles--get-requested
Get a list of all currently requested Power Profiles. Note that if any of the profiles conflict, then not
all may be enforced.
6)SetRequestedProfilesnvidia-smipower-profiles-sr<ProfileID>nvidia-smipower-profiles--set-requested<ProfileID(s)>
Adds the input profile(s) to the list of requested Power Profiles. The input is a comma separated list of
profile IDs with no spaces. Requires root.
7)ClearRequestedProfilesnvidia-smipower-profiles-cr<ProfileID>nvidia-smipower-profiles--clear-requested<ProfileID(s)>
Removes the input profile(s) to the list of requested Power Profiles. The input is a comma separated list
of profile IDs with no spaces. Requires root.
8)GetEnforcedProfilesnvidia-smipower-profiles-genvidia-smipower-profiles--get-enforced
Get a list of all currently enforced Power Profiles. Note that this list may differ from the requested
Profiles list if multiple conflicting profiles are selected.
Install Now
PNG Icons
