From: Christoph Hellwig <hch@infradead.org>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] fix topology initialization
Date: Fri, 17 Oct 2003 18:37:20 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106641601200638@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106641334730082@msgid-missing>
On Fri, Oct 17, 2003 at 11:27:07AM -0700, Jesse Barnes wrote:
> On Fri, Oct 17, 2003 at 07:05:11PM +0100, Christoph Hellwig wrote:
> > On Fri, Oct 17, 2003 at 10:48:34AM -0700, Jesse Barnes wrote:
> > > Now that NUMA kernels are working we can properly initialze the topology
> > > information so that /sys/devices/system/node* & friends aren't empty.
> >
> > So with a proper topology API we can start to kill off the topology-related
> > hwgfs mess?
>
> I think this will provide some of the info that hwgfs provides, but not
> all. We still need a way to map PCI busses to nodes (or cpumasks,
> whatever makes sense)
We should have this in the topology API already in a generic fashion. Do you
need it in userland aswell?
> and a way to map nodes & busses to physical, rack mounted bricks.
Well, that's a SN-specific thing. But it could be implemented similar to the
current toplogy API. What do you actually need this for?
next prev parent reply other threads:[~2003-10-17 18:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-17 17:48 [PATCH] fix topology initialization Jesse Barnes
2003-10-17 17:50 ` Jesse Barnes
2003-10-17 18:05 ` Christoph Hellwig
2003-10-17 18:27 ` Jesse Barnes
2003-10-17 18:34 ` Martin K. Petersen
2003-10-17 18:37 ` Christoph Hellwig [this message]
2003-10-17 18:51 ` Martin K. Petersen
2003-10-17 19:22 ` Chen, Kenneth W
2003-10-17 20:33 ` Jesse Barnes
2003-10-20 8:43 ` Jes Sorensen
2003-10-20 15:09 ` Martin K. Petersen
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=marc-linux-ia64-106641601200638@msgid-missing \
--to=hch@infradead.org \
--cc=linux-ia64@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.