Comment 4 for bug 1616024

Revision history for this message
Andreas Hasenack (ahasenack) wrote : Re: [16.04 FEAT] Add new package numcatl for s390x

xenial verification

Package is in proposed:

ubuntu@xenial-andreas:~$ apt-cache policy numactl
numactl:
  Installed: (none)
  Candidate: 2.0.11-1ubuntu1.1
  Version table:
     2.0.11-1ubuntu1.1 500
        500 http://ports.ubuntu.com/ubuntu-ports xenial-proposed/main s390x Packages

Package is installable:
ubuntu@xenial-andreas:~$ sudo apt install numactl
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  libnuma1
The following NEW packages will be installed:
  libnuma1 numactl
0 upgraded, 2 newly installed, 0 to remove and 49 not upgraded.
Need to get 52.4 kB of archives.
After this operation, 216 kB of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://ports.ubuntu.com/ubuntu-ports xenial-proposed/main s390x libnuma1 s390x 2.0.11-1ubuntu1.1 [20.9 kB]
Get:2 http://ports.ubuntu.com/ubuntu-ports xenial-proposed/main s390x numactl s390x 2.0.11-1ubuntu1.1 [31.5 kB]
Fetched 52.4 kB in 0s (164 kB/s)
Selecting previously unselected package libnuma1:s390x.
(Reading database ... 46566 files and directories currently installed.)
Preparing to unpack .../libnuma1_2.0.11-1ubuntu1.1_s390x.deb ...
Unpacking libnuma1:s390x (2.0.11-1ubuntu1.1) ...
Selecting previously unselected package numactl.
Preparing to unpack .../numactl_2.0.11-1ubuntu1.1_s390x.deb ...
Unpacking numactl (2.0.11-1ubuntu1.1) ...
Processing triggers for libc-bin (2.23-0ubuntu9) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up libnuma1:s390x (2.0.11-1ubuntu1.1) ...
Setting up numactl (2.0.11-1ubuntu1.1) ...
Processing triggers for libc-bin (2.23-0ubuntu9) ...

commands run:
ubuntu@xenial-andreas:~$ numactl
usage: numactl [--all | -a] [--interleave= | -i <nodes>] [--preferred= | -p <node>]
               [--physcpubind= | -C <cpus>] [--cpunodebind= | -N <nodes>]
               [--membind= | -m <nodes>] [--localalloc | -l] command args ...
       numactl [--show | -s]
       numactl [--hardware | -H]
       numactl [--length | -l <length>] [--offset | -o <offset>] [--shmmode | -M <shmmode>]
               [--strict | -t]
               [--shmid | -I <id>] --shm | -S <shmkeyfile>
               [--shmid | -I <id>] --file | -f <tmpfsfile>
               [--huge | -u] [--touch | -T]
               memory policy | --dump | -d | --dump-nodes | -D

memory policy is --interleave | -i, --preferred | -p, --membind | -m, --localalloc | -l
<nodes> is a comma delimited list of node numbers or A-B ranges or all.
Instead of a number a node can also be:
  netdev:DEV the node connected to network device DEV
  file:PATH the node the block device of path is connected to
  ip:HOST the node of the network device host routes through
  block:PATH the node of block device path
  pci:[seg:]bus:dev[:func] The node of a PCI device
<cpus> is a comma delimited list of cpu numbers or A-B ranges or all
all ranges can be inverted with !
all numbers and ranges can be made cpuset-relative with +
the old --cpubind argument is deprecated.
use --cpunodebind or --physcpubind instead
<length> can have g (GB), m (MB) or k (KB) suffixes

ubuntu@xenial-andreas:~$ sudo numastat
                           node0
numa_hit 475163
numa_miss 0
numa_foreign 0
interleave_hit 9452
local_node 475163
other_node 0