From: Denys Vlasenko <vda.linux@googlemail.com>
To: Matt Mackall <mpm@selenic.com>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Jeremy Fitzhardinge <jeremy@goop.org>,
David Rientjes <rientjes@google.com>,
John Berthels <jjberthels@gmail.com>,
Nick Piggin <nickpiggin@yahoo.com.au>
Subject: Re: [RFC][PATCH] /proc/<pid>/pmaps - memory maps in granularity of pages
Date: Wed, 5 Sep 2007 13:24:59 +0100 [thread overview]
Message-ID: <200709051324.59283.vda.linux@googlemail.com> (raw)
In-Reply-To: <20070814162618.GV30556@waste.org>
On Tuesday 14 August 2007 17:26, Matt Mackall wrote:
> On Tue, Aug 14, 2007 at 04:52:04PM +0800, Fengguang Wu wrote:
> > Here is a sample output:
> >
> > # cat /proc/$$/pmaps
> > 080c9000-080f6000 rwxp 080c9000 00:00 0 [heap]
> > 32969 45 Y_A_P__ 1
...
> > f7de1000-f7de3000 rwxp 00011000 03:00 176630 /lib/libnsl-2.3.6.so
> > 17 2 Y_A_P__ 1
> > [...]
>
> That's a _lot_ of data to generate and parse. I doubt we can watch a
> larger app in realtime with this interface. And it doesn't give us
> physical page numbers either.
> > 080c9000-080f6000 rwxp 080c9000 00:00 0 [heap]
> > 32969 45 Y_A_P__ 1
^^^^^ ^^
> > f7dba000-f7dc3000 r-xp 00000000 03:00 176633 /lib/libnss_files-2.3.6.so
^^ ^^ ^^^^^^
Since it's a new /proc file, we are not bound by compatibility.
Export *all* numbers in hex, and ensure that they are always even-chars wide
("fff" bad, "0fff" good). This way you can do binary<->string conversions
(both in kernel and in userspace) 8 bits per CPU cycle, or even faster.
--
vda
prev parent reply other threads:[~2007-09-05 12:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070814085204.GA10884@mail.ustc.edu.cn>
2007-08-14 8:52 ` Fengguang Wu
2007-08-14 16:26 ` Matt Mackall
[not found] ` <20070816013701.GA5209@mail.ustc.edu.cn>
2007-08-16 1:37 ` Fengguang Wu
[not found] ` <20070816031539.GA5110@mail.ustc.edu.cn>
2007-08-16 3:15 ` Fengguang Wu
2007-09-05 12:24 ` Denys Vlasenko [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=200709051324.59283.vda.linux@googlemail.com \
--to=vda.linux@googlemail.com \
--cc=akpm@linux-foundation.org \
--cc=jeremy@goop.org \
--cc=jjberthels@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=nickpiggin@yahoo.com.au \
--cc=rientjes@google.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
Powered by JetHome