From: Dave Hansen <haveblue@us.ibm.com>
To: Christoph Lameter <clameter@engr.sgi.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 10:20:33 -0700 [thread overview]
Message-ID: <1121102433.15095.26.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.62.0507081410520.16934@schroedinger.engr.sgi.com>
On Fri, 2005-07-08 at 14:11 -0700, Christoph Lameter wrote:
> I inherited a large code base from Ray for page migration. There was a
> small patch in there that I find to be very useful since it allows the display
> of the locality of the pages in use by a process. I reworked that patch and came
> up with a /proc/<pid>/numa_maps that gives more information about the vma's of
> a process. numa_maps is indexes by the start address found in /proc/<pid>/maps.
> F.e. with this patch you can see the page use of the "getty" process:
That looks quite useful. However, it *is* confined to helping NUMA
systems, and I think some modifications could allow it to be used for
memory hotplug.
We're planning to have memory laid out
in /sys/devices/system/memory/memoryXXX, where each memory object has a
fixed size. If NUMA is on, these objects also point back to their
owning NUMA node.
So, if something like numa_maps existed, but pointed to the memory
object instead of the NUMA node directly, you could still easily derive
the NUMA node. But, you'd also get information about which particular
bits of memory are being used. That might be useful for a user that's
getting desperate to remove some memory and wants to kill some processes
that might be less than willing to release that memory.
The downside is that we'll have to get that sysfs stuff working for !
SPARSEMEM configurations.
-- Dave
--
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>
next prev parent reply other threads:[~2005-07-11 17:20 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 [this message]
2005-07-11 18:02 ` Christoph Lameter
2005-07-11 20:31 ` Dave Hansen
2005-07-11 21:16 ` Christoph Lameter
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=1121102433.15095.26.camel@localhost \
--to=haveblue@us.ibm.com \
--cc=clameter@engr.sgi.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