diff options
| author | Franck Cuny <franck@fcuny.net> | 2024-03-06 06:29:24 -0800 |
|---|---|---|
| committer | Franck Cuny <franck@fcuny.net> | 2024-03-06 06:29:24 -0800 |
| commit | 1e4a5aa09c1c8f43722c9c260f011398799a8e8f (patch) | |
| tree | cd73e0fb8ba53bd21cee6ccf2dcc85639bbbb93f /tools/numap/README.org | |
| parent | set correct git email in the profiles (diff) | |
| download | infra-1e4a5aa09c1c8f43722c9c260f011398799a8e8f.tar.gz | |
rename `tools` to `packages` to follow convention
The convention is to use `pkgs` or `packages` for overlays and
definition of custom packages. Since I'm already using `pkg` for go,
I prefer to use `packages` for my scripts.
Diffstat (limited to 'tools/numap/README.org')
| -rw-r--r-- | tools/numap/README.org | 47 |
1 files changed, 0 insertions, 47 deletions
diff --git a/tools/numap/README.org b/tools/numap/README.org deleted file mode 100644 index c7941b1..0000000 --- a/tools/numap/README.org +++ /dev/null @@ -1,47 +0,0 @@ -#+TITLE: numap - -Print the NUMA topology of a host. - -* Usage -#+BEGIN_SRC sh -./numap |jq . -{ - "node0": { - "name": "node0", - "path": "/sys/devices/system/node/node0", - "cpulist": "0-19,40-59", - "pci_devices": [ - { - "vendor": "Mellanox Technologies", - "name": "MT27710 Family [ConnectX-4 Lx]" - }, - { - "vendor": "Mellanox Technologies", - "name": "MT27710 Family [ConnectX-4 Lx]" - } - ] - }, - "node1": { - "name": "node1", - "path": "/sys/devices/system/node/node1", - "cpulist": "20-39,60-79", - "pci_devices": [ - { - "vendor": "Intel Corporation", - "name": "NVMe Datacenter SSD [3DNAND, Beta Rock Controller]" - } - ] - } -} -#+END_SRC - -The command will scan the host to find the NUMA nodes, and all the PCI devices, and map the PCI devices back to the NUMA node. - -It also provides a way to see the list of CPUs attached to the node. - -* Limitations -** Device class -For now only the following classes of hardware are cared for: -- NVMe -- network -- GPU |
