From: "Ray Lee" <ray-lk@madrabbit.org>
To: "Fengguang Wu" <wfg@mail.ustc.edu.cn>
Cc: "Andrew Morton" <akpm@osdl.org>, "Matt Mackall" <mpm@selenic.com>,
"John Berthels" <jjberthels@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] process memory footprint info in proc/<pid>/[s|p]maps v2
Date: Sun, 19 Aug 2007 20:15:01 -0700 [thread overview]
Message-ID: <2c0942db0708192015u2759ccfby320549cd6393dff3@mail.gmail.com> (raw)
In-Reply-To: <387510147.18695@ustc.edu.cn>
On 8/19/07, Fengguang Wu <wfg@mail.ustc.edu.cn> wrote:
> Inspired by Matt Mackall's pagemap patches and ideas, I worked up these
> textual interfaces that achieve the same goals. The patches run OK
> under different sized reads.
[...]
> 2b7d6e8f3000-2b7d6ea40000 r-xp 00000000 08:01 1564031 /lib/libc-2.6.so
> 0 2 YRAU___ 81
> 2 1 YRAU___ 80
> 3 1 YRAU___ 81
> 4 1 YRAU___ 72
> 5 1 YRAU___ 77
> 6 1 YRAU___ 79
> 7 1 YRAU___ 73
> 8 1 YRAU___ 79
> 9 1 YRAU___ 78
> a 1 YRAU___ 77
> b 1 YRAU___ 72
> c 1 YRAU___ 75
> d 1 YRAU___ 81
> e 1 YRAU___ 72
> f 1 YRAU___ 78
> 10 1 YRAU___ 81
> 11 1 YRAU___ 78
> 12 1 YRAU___ 80
> 13 1 YRAU___ 78
> 14 2 YRAU___ 81
> 16 1 YRAU___ 49
> 17 6 YRAU___ 41
> 1d 1 YRAU___ 80
> 2a 1 YRAU___ 44
> 2b 1 YRAU___ 69
> 2c 1 YRAU___ 28
> 31 1 YRAU___ 79
> 32 1 YRAU___ 49
> 33 1 YRAU___ 73
> 34 1 YRAU___ 57
> 35 1 YRAU___ 67
> 42 1 YRAU___ 77
> 43 3 YRAU___ 78
> 46 1 YRAU___ 77
> 47 1 YRAU___ 70
> 48 1 YRAU___ 15
> 4d 1 YRAU___ 78
> 5f 1 YRAU___ 78
> 60 1 YRAU___ 75
> 61 1 YRAU___ 72
> 62 1 YRAU___ 67
> 63 1 YRAU___ 59
> 68 1 YRAU___ 63
> 69 1 YRAU___ 61
> 6a 1 YRAU___ 63
> 6b 1 YRAU___ 75
> 6c 1 YRAU___ 76
> 6d 1 YRAU___ 81
> 6e 1 YRAU___ 77
> 6f 1 YRAU___ 79
> 70 1 YRAU___ 44
> 71 1 YRAU___ 79
> 72 1 YRAU___ 78
> 73 1 YRAU___ 79
> 74 1 YRAU___ 46
> 75 1 YRAU___ 78
> 76 1 YRAU___ 60
> 78 1 YRAU___ 79
> 79 1 YRAU___ 81
> 7a 1 YRAU___ 80
> 7e 1 YRAU___ 41
> 8a 1 YRAU___ 36
> 8b 1 YRAU___ 72
> 8c 1 YRAU___ 28
> 8d 1 YRAU___ 21
> 91 2 YRAU___ 19
> 99 1 YRAU___ 62
> 9a 1 YRAU___ 76
> 9b 1 YRAU___ 72
> c4 1 YRAU___ 80
> c5 1 YRAU___ 82
> c6 1 YRAU___ 81
> cb 1 YRAU___ 42
> cc 1 YRAU___ 79
> cd 1 YRAU___ 26
> cf 1 YRAU___ 12
> d0 1 YRAU___ 77
> d1 1 YRAU___ 38
> d2 1 YRAU___ 45
> d3 1 YRAU___ 66
> d4 1 YRAU___ 71
> e0 1 YRAU___ 52
> 106 1 YRAU___ 33
> 107 1 YRAU___ 14
> 108 1 YRAU___ 63
> 109 1 YRAU___ 57
> 10b 1 YRAU___ 70
> 10c 1 YRAU___ 63
> 118 1 YRAU___ 65
> 119 1 YRAU___ 78
> 11a 1 YRAU___ 69
> 11b 1 YRAU___ 68
> 11e 2 YRAU___ 62
> 120 1 YRAU___ 74
> 121 1 YRAU___ 42
> 125 1 YRAU___ 17
Eh, I'd think that pivoting the data set would be a much more natural
(& therefore shorter) representation.
YRAU___ 0,2:81 2:80 3:81 4:72 5:77 6:79 7:73 8:79 9:78
...versus...
> 0 2 YRAU___ 81
> 2 1 YRAU___ 80
> 3 1 YRAU___ 81
> 4 1 YRAU___ 72
> 5 1 YRAU___ 77
> 6 1 YRAU___ 79
> 7 1 YRAU___ 73
> 8 1 YRAU___ 79
> 9 1 YRAU___ 78
So, flags followed by a list of offset[,length]:usage. If the flags
change, start a new line. If you get a line that's too long, start a
new line.
No?
next prev parent reply other threads:[~2007-08-20 3:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070819075410.411207640@mail.ustc.edu.cn>
2007-08-19 7:54 ` Fengguang Wu
2007-08-20 3:15 ` Ray Lee [this message]
[not found] ` <20070820075515.GA10476@mail.ustc.edu.cn>
2007-08-20 7:55 ` Fengguang Wu
[not found] ` <20070819075547.445659254@mail.ustc.edu.cn>
2007-08-19 7:54 ` [PATCH 1/4] maps: PSS(proportional set size) accounting in smaps Fengguang Wu
[not found] ` <20070819075547.562443204@mail.ustc.edu.cn>
2007-08-19 7:54 ` [PATCH 2/4] maps: address based vma walking Fengguang Wu
[not found] ` <20070819075547.674060890@mail.ustc.edu.cn>
2007-08-19 7:54 ` [PATCH 3/4] maps: introduce generic_maps_open() Fengguang Wu
[not found] ` <20070819075547.785390741@mail.ustc.edu.cn>
2007-08-19 7:54 ` [PATCH 4/4] maps: /proc/<pid>/pmaps interface - memory maps in granularity of pages Fengguang Wu
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=2c0942db0708192015u2759ccfby320549cd6393dff3@mail.gmail.com \
--to=ray-lk@madrabbit.org \
--cc=akpm@osdl.org \
--cc=jjberthels@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=wfg@mail.ustc.edu.cn \
/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®