"cpuset -n prefer:?" --what values for "?" are supposed to be allowed? (only 1 is, despite two numa domains)

[Mark Millard]

On 2019-Sep-11, at 07:31, Mark Johnston <markj at freebsd.org> wrote:

> On Tue, Sep 10, 2019 at 10:58:05PM -0700, Mark Millard wrote:
>> In a context with:
>> 
>> # cpuset -g
>> pid -1 mask: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27
>> pid -1 domain policy: first-touch mask: 0, 1
>> 
>> I get:
>> 
>> # cpuset -l0 -n prefer:0 COMMAND
>> cpuset: setdomain: Invalid argument
>> 
>> # cpuset -l0 -n prefer:2 COMMAND
>> cpuset: setdomain: Invalid argument
>> 
>> But one prefer:? value does allow the COMMAND
>> to run:
>> 
>> # cpuset -l0 -n prefer:1 COMMAND
>> 
>> This seem odd to me. Am I missing something?
>> 
>> For reference: I'm using a ThreadRipper 1950X
>> with a head -r351227 based context for this
>> activity. The above happens to have been run
>> in a Windows 10 Pro HyperV session, instead
>> of in a native-boot of the same media. (A
>> native-boot would have had 32 CPUs.)
> 
> Can you please show the output of "sysctl vm.phys_segs" from this
> setup?

Sure:

# sysctl vm.phys_segs
vm.phys_segs: 
SEGMENT 0:

start:     0x1000
end:       0x9f000
domain:    0
free list: 0xffffffff8281daa0

SEGMENT 1:

start:     0x103000
end:       0x1000000
domain:    0
free list: 0xffffffff8281daa0

SEGMENT 2:

start:     0x1000000
end:       0x2ee1000
domain:    0
free list: 0xffffffff8281d830

SEGMENT 3:

start:     0x2eea000
end:       0x2f23000
domain:    0
free list: 0xffffffff8281d830

SEGMENT 4:

start:     0x3000000
end:       0xf7ff0000
domain:    0
free list: 0xffffffff8281d830

SEGMENT 5:

start:     0x100002000
end:       0x9c5562000
domain:    0
free list: 0xffffffff8281d5c0

SEGMENT 6:

start:     0xa07c00000
end:       0xa07d50000
domain:    0
free list: 0xffffffff8281d5c0

SEGMENT 7:

start:     0xa08001000
end:       0xf9ee00000
domain:    1
free list: 0xffffffff8281dd10

SEGMENT 8:

start:     0x1000000000
end:       0x1427fe6000
domain:    1
free list: 0xffffffff8281dd10


And confirming the oddity is still the case
(I'd rebooted since the report):

# cpuset -g
pid -1 mask: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27
pid -1 domain policy: first-touch mask: 0, 1

# cpuset -l0 -n prefer:0 COMMAND
cpuset: setdomain: Invalid argument

# cpuset -l0 -n prefer:2 COMMAND
cpuset: setdomain: Invalid argument

# cpuset -l0 -n prefer:1 COMMAND
cpuset: COMMAND: No such file or directory


===
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)