From: Minchan Kim <minchan.kim@gmail.com>
To: Nikanth Karthikesan <knikanth@suse.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Matt Mackall <mpm@selenic.com>
Subject: Re: [PATCH] Export mlock information via smaps
Date: Tue, 17 Aug 2010 23:42:56 +0900 [thread overview]
Message-ID: <20100817144256.GC3884@barrios-desktop> (raw)
In-Reply-To: <201008171039.31070.knikanth@suse.de>
On Tue, Aug 17, 2010 at 10:39:31AM +0530, Nikanth Karthikesan wrote:
> Currently there is no way to find whether a process has locked its pages in
> memory or not. And which of the memory regions are locked in memory.
>
> Add a new field to perms field 'l' to export this information. The information
> exported via maps file is not changed.
>
> Signed-off-by: Nikanth Karthikesan <knikanth@suse.de>
Reviewed-by: Minchan Kim <minchan.kim@gmail.com>
Cced Matt.
It would be good if we have a such thing.
In addtion, code itself looks good to me. :)
But I have a question.
Why didn't you change /proc/map?
Due to ABI? So then, Is it okay to change smaps ABI?
I don't know there is any well-known tool to use smap information.
Maybe Matt have the answer.
--
Kind regards,
Minchan Kim
--
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:[~2010-08-17 14:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-17 5:09 [PATCH] Export mlock information via smaps Nikanth Karthikesan
2010-08-17 14:42 ` Minchan Kim [this message]
2010-08-17 16:25 ` Matt Mackall
2010-08-18 4:53 ` Nikanth Karthikesan
2010-08-18 5:52 ` Balbir Singh
2010-08-18 6:49 ` Nikanth Karthikesan
2010-08-18 6:56 ` Balbir Singh
2010-08-18 15:12 ` Wu Fengguang
2010-08-20 0:25 ` Andrew Morton
2010-08-20 21:57 ` Matt Mackall
2010-08-18 15:07 ` Wu Fengguang
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=20100817144256.GC3884@barrios-desktop \
--to=minchan.kim@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=knikanth@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mpm@selenic.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;
as well as URLs for NNTP newsgroup(s).