From: Mauricio Lin <mauriciolin@gmail.com>
To: Albert Cahalan <albert@users.sf.net>
Cc: linux-kernel mailing list <linux-kernel@vger.kernel.org>,
Andrew Morton OSDL <akpm@osdl.org>
Subject: Re: [PATCH] A new entry for /proc
Date: Tue, 1 Mar 2005 10:32:45 -0400 [thread overview]
Message-ID: <3f250c71050301063228f3507e@mail.gmail.com> (raw)
In-Reply-To: <1109271379.5125.180.camel@cube>
Hi,
> The most important thing about a /proc file format is that it has
> a documented means of being extended in the future. Without such
> documentation, it is impossible to write a reliable parser.
>
> The "Name: value" stuff is rather slow. Right now procps (ps, top, etc.)
> is using a perfect hash function to parse the /proc/*/status files.
> ("man gperf") This is just plain gross, but needed for decent performance.
So, change the output format is important, right?
> Extending the /proc/*/maps file might be possible. It is commonly used
> by debuggers I think, so you'd better at least verify that gdb is OK.
> The procps "pmap" tool uses it too. To satisfy the procps parser:
>
> a. no more than 31 flags
> b. no '/' prior to the filename
> c. nothing after the filename
> d. no new fields inserted prior to the inode number
>
Yes, probably smaps is more feasible for tracking environment. Do you
know any public kernel (I mean kernel version for tracking and
debugging) where can I post the smaps PATCH in order to be included?
BR,
Mauricio Lin.
next prev parent reply other threads:[~2005-03-01 14:33 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-24 18:56 [PATCH] A new entry for /proc Albert Cahalan
2005-03-01 14:32 ` Mauricio Lin [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-06 21:11 Mauricio Lin
2005-01-07 4:23 ` Andrew Morton
2005-01-07 12:30 ` Roger Luethi
2005-01-08 20:20 ` Hugh Dickins
2005-01-08 21:47 ` Alan Cox
2005-01-10 9:21 ` Edjard Souza Mota
2005-01-10 15:23 ` Mauricio Lin
2005-02-22 13:13 ` Mauricio Lin
2005-02-24 8:31 ` Mauricio Lin
2005-02-24 9:09 ` Andrew Morton
2005-02-24 11:43 ` Mauricio Lin
2005-02-24 11:52 ` Andrew Morton
2005-02-25 15:14 ` Mauricio Lin
2005-02-28 9:43 ` Mauricio Lin
2005-02-28 9:56 ` Mauricio Lin
2005-02-28 20:41 ` Hugh Dickins
2005-03-01 8:08 ` Mauricio Lin
2005-03-01 14:17 ` Mauricio Lin
2005-03-01 15:44 ` Mauricio Lin
2005-03-02 12:20 ` Mauricio Lin
2005-03-02 19:07 ` Hugh Dickins
2005-03-03 7:25 ` Mauricio Lin
2005-03-03 12:48 ` Hugh Dickins
2005-03-03 14:23 ` Mauricio Lin
2005-01-10 14:35 ` Mauricio Lin
2005-01-14 22:46 ` Mauricio Lin
[not found] ` <20050114154209.6b712e55.akpm@osdl.org>
2005-01-17 18:03 ` Mauricio Lin
2005-01-17 19:02 ` Mauricio Lin
2005-01-17 17:30 ` Marcelo Tosatti
2005-01-17 21:27 ` Mauricio Lin
2005-01-17 21:35 ` William Lee Irwin III
2005-01-18 1:07 ` Nick Piggin
2005-01-19 12:59 ` Nick Piggin
2005-01-24 22:14 ` Mauricio Lin
2005-04-29 18:36 ` Mauricio Lin
2005-04-30 1:25 ` Andrew Morton
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=3f250c71050301063228f3507e@mail.gmail.com \
--to=mauriciolin@gmail.com \
--cc=akpm@osdl.org \
--cc=albert@users.sf.net \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.