From: Christoph Lameter <clameter@sgi.com>
To: Nick Piggin <npiggin@suse.de>
Cc: Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [patch] mm: make mincore work for general mappings
Date: Wed, 31 Jan 2007 12:20:00 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0701311218390.30567@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20070130113720.GA3038@wotan.suse.de>
On Tue, 30 Jan 2007, Nick Piggin wrote:
> Make mincore work for anon mappings, nonlinear, and migration entries.
> Based on patch from Linus Torvalds <torvalds@linux-foundation.org>.
There are certain similarities with /proc/pid/numa_maps. See
mm/mempolicy.c. Could we consolidate the code somehow (maybe also with
smaps) and have one way of scanning the pages of a process?
--
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:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-01-31 20:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-30 11:37 [patch] mm: make mincore work for general mappings Nick Piggin
2007-01-31 20:20 ` Christoph Lameter [this message]
2007-02-02 2:04 ` Nick Piggin
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.64.0701311218390.30567@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=linux-mm@kvack.org \
--cc=npiggin@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).