From: Mike Travis <travis@sgi.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Bian LuLu <helianthus.lu@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: [RFC] The meaning of local_cpulist and local_cpus
Date: Wed, 24 Apr 2013 09:56:58 -0700 [thread overview]
Message-ID: <51780EDA.3000003@sgi.com> (raw)
In-Reply-To: <CAErSpo5VaiuH+WT4RdM9yU9AHMkUKzATMiNzhixRU04_aZusBg@mail.gmail.com>
On 4/24/2013 9:48 AM, Bjorn Helgaas wrote:
> [+cc linux-pci, Mike]
>
> On Wed, Apr 24, 2013 at 4:06 AM, Bian LuLu <helianthus.lu@gmail.com> wrote:
>> Hi all,
>>
>> Recently, i read some codes of PCI portions. I think
>> local_cpulist is a list about one kind of CPU and
>> local_cpus is a mask of CPU. But i am not sure when
>> and how i should use these two parameters.
>>
>> See http://lxr.linux.no/linux+v3.5.4/drivers/pci/pci-sysfs.c#L390 for
>> details.
>>
>> Would anyone please give me some suggestions?
>> Thanks in advance ;-)
>
> I don't know off-hand, but maybe Mike or somebody on linux-pci does.
> It looks like Mike added local_cpulist with 39106dcf85.
>
It primarily comes into play when you have a large # of cpus.
Here's the difference on a system that has 1024 cpu threads:
harp31-sys:/sys/devices/system/node/node20 # cat cpulist
160-167,672-679
harp31-sys:/sys/devices/system/node/node20 # cat cpumap
00000000,00000000,00000000,00000000,00000000,00000000,00000000,
00000000,00000000,00000000,000000ff,00000000,00000000,00000000,
00000000,00000000,00000000,00000000,00000000,00000000,00000000,
00000000,00000000,00000000,00000000,00000000,000000ff,00000000,
00000000,00000000,00000000,00000000
Which is easier to interpret? :)
But there are some older user side utilities that still
use the mask format.
next prev parent reply other threads:[~2013-04-24 16:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-24 10:06 [RFC] The meaning of local_cpulist and local_cpus Bian LuLu
2013-04-24 16:48 ` Bjorn Helgaas
2013-04-24 16:56 ` Mike Travis [this message]
2013-04-25 13:57 ` Bian LuLu
2013-04-25 14:17 ` Mike Travis
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=51780EDA.3000003@sgi.com \
--to=travis@sgi.com \
--cc=bhelgaas@google.com \
--cc=helianthus.lu@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.