From: Christoph Lameter <clameter@engr.sgi.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: linux-mm <linux-mm@kvack.org>,
ia64 list <linux-ia64@vger.kernel.org>,
pj@sgi.com
Subject: Re: [NUMA] /proc/<pid>/numa_maps to show on which nodes pages reside
Date: Mon, 11 Jul 2005 14:16:54 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.62.0507111415420.23319@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <1121113875.15095.45.camel@localhost>
On Mon, 11 Jul 2005, Dave Hansen wrote:
> Well, my point was that, if we have two, the numa_maps can be completely
> derived in userspace from the information in memory_maps plus sysfs
> alone. So, why increase the kernel's complexity with two
> implementations that can do the exact same thing? Yes, it might make
> the batch scheduler do one more pathname lookup, but that's not the
> kernel's problem :)
>
> BTW, are you planning on using SPARSEMEM whenever NUMA is enabled in the
> future?
I am not sure if we will be using SPARSEMEM or not.
It would not be good to make the numa_maps patch depend on SPARSEMEM since
that is an optional feature right now.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
prev parent reply other threads:[~2005-07-11 21:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-08 21:11 Christoph Lameter
2005-07-11 17:20 ` Dave Hansen
2005-07-11 18:02 ` Christoph Lameter
2005-07-11 20:31 ` Dave Hansen
2005-07-11 21:16 ` Christoph Lameter [this message]
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=Pine.LNX.4.62.0507111415420.23319@schroedinger.engr.sgi.com \
--to=clameter@engr.sgi.com \
--cc=haveblue@us.ibm.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pj@sgi.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