public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: jbarnes@sgi.com (Jesse Barnes)
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] fix topology initialization
Date: Fri, 17 Oct 2003 20:33:23 +0000	[thread overview]
Message-ID: <marc-linux-ia64-106642289105919@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106641334730082@msgid-missing>

On Fri, Oct 17, 2003 at 07:37:20PM +0100, Christoph Hellwig wrote:
> > 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?

Yeah, it might be useful for a userland irq balancer for example.

> > 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?

Well, I'm not sure that it should be in the kernel at all.  Maybe it
could just be a SAL call or something with a thin driver wrapper for a
userspace program to use.  It's mainly useful for physically locating
things, e.g.  'the PCI slot on this brick on this rack is dead'.

Jesse

  parent reply	other threads:[~2003-10-17 20:33 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
2003-10-17 18:51 ` Martin K. Petersen
2003-10-17 19:22 ` Chen, Kenneth W
2003-10-17 20:33 ` Jesse Barnes [this message]
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-106642289105919@msgid-missing \
    --to=jbarnes@sgi.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox