From: Jesse Barnes <jbarnes@sgi.com>
To: Anton Blanchard <anton@samba.org>
Cc: linux-kernel@vger.kernel.org, ak@suse.de, greg@kroah.com,
miltonm@bga.com
Subject: Re: 3 ways to represent cpu affinity in /sys and counting
Date: Thu, 30 Dec 2004 11:40:19 -0800 [thread overview]
Message-ID: <200412301140.20366.jbarnes@sgi.com> (raw)
In-Reply-To: <20041226002744.GC21710@krispykreme.ozlabs.ibm.com>
On Saturday, December 25, 2004 4:27 pm, Anton Blanchard wrote:
> Hi,
>
> We have a patch to change pcibus_to_cpumask to pcibus_to_node. This makes
> it more consistent with cpu_to_node, and when you want a cpumask you
> use node_to_cpumask.
Great! I think Matt Dobson said he was going to do something similar, but he
got sidetracked (and iirc, ak also didn't like the idea). FWIW, I like it,
with the caveat that the node returned from pcibus_to_node may not have any
memory or CPUs associated with it.
> A pci device has a local_cpus property:
>
> /sys/devices/pci000a:00/000a:00:02.6/local_cpus
>
> A pci_bus has a cpuaffinity property:
>
> /sys/class/pci_bus/000d:d8/cpuaffinity
I don't know how these two got different names...
> A node has a cpumap property:
>
> /sys/devices/system/node/node3/cpumap
>
> Can we standardize on a single property name for this? :)
Seems like nodes should have a cpumap and PCI busses should have a node.
> Furthermore, looking at node linkages:
>
> A node has symlinks to cpus:
>
> /sys/devices/system/node/node0/cpu0 -> /sys/devices/system/cpu/cpu0
>
> But doesnt have symlinks to pci devices.
Yep, this would be nice to have.
Jesse
next prev parent reply other threads:[~2004-12-30 19:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-26 0:27 3 ways to represent cpu affinity in /sys and counting Anton Blanchard
2004-12-30 19:40 ` Jesse Barnes [this message]
2005-01-03 15:15 ` Andi Kleen
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=200412301140.20366.jbarnes@sgi.com \
--to=jbarnes@sgi.com \
--cc=ak@suse.de \
--cc=anton@samba.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miltonm@bga.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