From: jbarnes@sgi.com (Jesse Barnes)
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] fix topology init take 2
Date: Mon, 20 Oct 2003 15:35:45 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106666451508513@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106641524132220@msgid-missing>
On Mon, Oct 20, 2003 at 05:17:29PM +0200, Xavier Bru wrote:
>
> Jesse Barnes writes:
> > Populate topology directories correctly now that NUMA kernels work.
> >
> > Jesse
> >
>
> Jesse,
>
> Thanks for the patch. Just one question about it:
>
> Are there relevant informations that can be used apart from:
> node*/meminfo
> node*/cpumap
>
> We find some node*/memblk* and cpu/cpu* that are empty directories.
>
> Should they sometimes provide some informations like LID (for cpu*) or
> physical block addr & length (for memblk) ? I suppose this is part of
> the discussion on libnuma & hwgfs ?
Those seem like reasonable things to export in those directories, is
there anything else that would be nice to have?
Jesse
next prev parent reply other threads:[~2003-10-20 15:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-17 18:25 [PATCH] fix topology init take 2 Jesse Barnes
2003-10-20 15:17 ` Xavier Bru
2003-10-20 15:35 ` Jesse Barnes [this message]
2003-10-20 17:13 ` Xavier Bru
2003-10-20 20:50 ` Andreas Schwab
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-106666451508513@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