diff options
| author | Matthew Wilcox <willy@linux.intel.com> | 2015-04-22 16:27:21 -0400 |
|---|---|---|
| committer | Martin Mares <mj@ucw.cz> | 2015-09-14 16:43:15 +0200 |
| commit | 90ec4a6d0ae85ccd018be3da2d080f602fc56ca7 (patch) | |
| tree | 0794a59d692d0442f1bc191eb5f644f1359e200a /lspci.man | |
| parent | c8b1fb09a992a76e0d7fd30bf291e95c5033b71d (diff) | |
| download | pciutils-90ec4a6d0ae85ccd018be3da2d080f602fc56ca7.tar.gz | |
Report NUMA node in lspci -v
In multi-socket systems, it's useful to see which node a particular
PCI device belongs to. Linux provides this information through sysfs,
but some users don't like poking through sysfs themselves to find it,
and it's pretty straightforward to report it in lspci.
I should note that when there is no NUMA node for a particular device,
Linux reports -1. I've chosen to continue that convention in pciutils,
and simply omit the information if the device does not belong to a NUMA
node (eg on single-socket systems, or devices which are not preferentially
attached to a particular node, like Nehalem-based systems).
Diffstat (limited to 'lspci.man')
0 files changed, 0 insertions, 0 deletions