Stack Exchange network consists of 183 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
Visit Stack Exchange
Stack Internal
Knowledge at work
Bring the best of human thought and AI automation together at your work.
Explore Stack Internal I think if you use the --show switch it might make more sense:
$ numactl --show policy: default preferred node: current physcpubind: 0 1 2 3 cpubind: 0 nodebind: 0 membind: 0 So you can control the use of physcpubind's like this:
$ numactl --physcpubind=+0-2 myapp This would limit the application myapp to the first 2 CPU cores. My system is an i5 with 4 cores.
I think if you use the --show switch it might make more sense:
$ numactl --show policy: default preferred node: current physcpubind: 0 1 2 3 cpubind: 0 nodebind: 0 membind: 0 So you can control the use of physcpubind's like this:
$ numactl --physcpubind=+0-2 myapp This would limit the application myapp to the first 2 CPU cores. My system is an i5 with 4 cores.
I think if you use the --show switch it might make more sense:
$ numactl --show policy: default preferred node: current physcpubind: 0 1 2 3 cpubind: 0 nodebind: 0 membind: 0 So you can control the use of physcpubind's like this:
$ numactl --physcpubind=+0-2 myapp This would limit the application myapp to the first 2 CPU cores. My system is an i5 with 4 cores.
I think if you use the --show switch it might make more sense:
$ numactl --show policy: default preferred node: current physcpubind: 0 1 2 3 cpubind: 0 nodebind: 0 membind: 0 So you can control the use of physcpubind's like this:
$ numactl --physcpubind=+0-2 myapp This would limit the application myapp to the first 2 CPU cores. My system is an i5 with 4 cores.