From: Andi Kleen <andi@firstfloor.org>
To: "MacCana, Mike" <mike.maccana@credit-suisse.com>
Cc: linux-numa@vger.kernel.org
Subject: Re: Possible man numactl error?
Date: Thu, 11 Feb 2010 15:40:51 +0100 [thread overview]
Message-ID: <20100211144051.GN2777@one.firstfloor.org> (raw)
In-Reply-To: <5608FA8A997F1A46B7E985494F8478DD079309DA@ELON17P32003A.csfb.cs-group.com>
On Thu, Feb 11, 2010 at 02:26:14PM -0000, MacCana, Mike wrote:
> I've spotted what appears to be an inconsistency between man numactl and
> /proc & /sys.
>
> --physcpubind=cpus, -C cpus
> Only execute process on cpus. This accepts physical
> cpu numbers as shown in the processor fields of /proc/cpuinfo.
"physical CPU" in this case means CPUs as shown by cpuinfo,
not APIC IDs or package ids or anything like that.
> However the processor field of /proc/cpuinfo refers to logical
> processors (ie, run queues), not physical ones. Eg:
I don't think the term 'logical CPU' or 'run queues'
is used anywhere in the kernel for CPU numbers.
Perhaps the man page could be clarified (mostly for people
who think too complicated like you :-) and yes perhaps
it is better in this age with all kinds of virtual CPUs
-Andi
next prev parent reply other threads:[~2010-02-11 14:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-11 14:26 Possible man numactl error? MacCana, Mike
2010-02-11 14:40 ` Andi Kleen [this message]
2010-02-11 14:49 ` MacCana, Mike
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100211144051.GN2777@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=linux-numa@vger.kernel.org \
--cc=mike.maccana@credit-suisse.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox