From: Hugh Dickins <hughd@google.com>
To: "Ren, Qiaowei" <qiaowei.ren@intel.com>
Cc: David Rientjes <rientjes@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Al Viro <viro@zeniv.linux.org.uk>,
Oleg Nesterov <oleg@redhat.com>,
Cyrill Gorcunov <gorcunov@openvz.org>,
Vasiliy Kulikov <segoon@openwall.com>,
Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
Konstantin Khlebnikov <khlebnikov@openvz.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH 1/1] proc: add /proc/pid/shmaps
Date: Wed, 8 Aug 2012 20:09:44 -0700 (PDT) [thread overview]
Message-ID: <alpine.LSU.2.00.1208081950080.1306@eggly.anvils> (raw)
In-Reply-To: <9E0BE1322F2F2246BD820DA9FC397ADE37A530@SHSMSX102.ccr.corp.intel.com>
On Thu, 9 Aug 2012, Ren, Qiaowei wrote:
> On Wed, 8 Aug 2012, David Rientjes wrote:
> > On Wed, 8 Aug 2012, Qiaowei Ren wrote:
> >
> > > Add a shmaps entry to /proc/pid: show information about shared memory in an address space.
> > >
> > > People that use shared memory and want to perform an analyzing about it. For example, judge whether any memory address is shared. This file just contains 'share' part of /proc/pid/maps now. There are too many contents in maps, and so we have to do a lot of analysis to obtain relative information every time.
> > >
> > > Signed-off-by: Qiaowei Ren <qiaowei.ren@intel.com>
> >
> > Nack as unnecessary; /proc/pid/maps already explicitly emits 's' for VM_MAYSHARE and 'p' otherwise so this information is already available to userspace.
> >
>
> Thanks for your reply. There are so many contents in /proc/pid/maps, and usually only a very small minority of those are about shared memory in address space of every process. So I hope that a new file maybe provide some convenience. Could you tell me how to get such information except analyzing 'maps' file?
You are joking? Please imagine what the kernel and /proc would look like
if it provided a personally tailored /proc file to everybody who could not
be bothered to parse the information already shown there.
Sure, there is already lots of ugly and duplicative junk under /proc,
which usually has to be kept to preserve back compatibility; but please
do not try to add to it.
There is sometimes an excuse if some fields of an existing /proc file are
significantly more expensive for the kernel to compute than others: then
a file which separates them can save processing. But that is definitely
not the case here.
A side issue would be whether parsing /proc/pid/maps for 's' VM_MAYSHARE
mappings (or your equivalent patch) actually tells you what you want to
know about "shared memory" - that would depend on what you really want
to know, and what you mean by shared memory.
Hugh
prev parent reply other threads:[~2012-08-09 3:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-08 13:04 Qiaowei Ren
2012-08-08 21:10 ` David Rientjes
2012-08-09 0:49 ` Ren, Qiaowei
2012-08-09 3:09 ` Hugh Dickins [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=alpine.LSU.2.00.1208081950080.1306@eggly.anvils \
--to=hughd@google.com \
--cc=akpm@linux-foundation.org \
--cc=gorcunov@openvz.org \
--cc=khlebnikov@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=oleg@redhat.com \
--cc=qiaowei.ren@intel.com \
--cc=rientjes@google.com \
--cc=segoon@openwall.com \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®