[Beowulf] Again about NUMA (numactl and taskset)
hahn at mcmaster.ca
Mon Jun 23 15:12:48 EDT 2008
> "how sure are we that a process (or thread) that allocated and initialized
> and writes to memory at a single specific memory node,
> also keeps getting scheduled at a core on that memory node?"
numactl --cpubind=0 --membind=0
> It seems to me that sometimes (like every second or so) threads jump from 1
> memory node to another. I could be wrong,
> but i certainly have that impression with the linux kernels.
you can always tie a thread to a core. for non-bound threads,
the question is really how long the kernel should leave a runnable thread
"on" a busy cpu before running it on another (idle) cpu. the kernel
does try to avoid this, but how hard has in the past depended on the
kernel's guess about the cache footprint of the thread and its "natural"
timeslice (how long it typically runs before yielding.)
Beowulf mailing list, Beowulf at beowulf.org
To change your subscription (digest mode or unsubscribe) visit http://www.beowulf.org/mailman/listinfo/beowulf
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
More information about the Beowulf