From: Hitoshi Mitake <mitake@dcl.info.waseda.ac.jp>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: fweisbec@gmail.com, linux-kernel@vger.kernel.org,
h.mitake@gmail.com, Paul Mackerras <paulus@samba.org>,
Ingo Molnar <mingo@elte.hu>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH] lockstat: export data in python expression
Date: Tue, 01 Mar 2011 08:48:49 +0900 [thread overview]
Message-ID: <4D6C3461.8010109@dcl.info.waseda.ac.jp> (raw)
In-Reply-To: <1298916475.5226.850.camel@laptop>
On 2011年03月01日 03:07, Peter Zijlstra wrote:
> On Tue, 2011-03-01 at 00:00 +0900, Hitoshi Mitake wrote:
>> I'm writing the tool for parsing and arranging the data of /proc/lock_stat
>> in python. But I soon found that lock_stat is hard to parse, so I wrote
>> this patch to let lock_stat output its information in python expression.
>
> _IF_ we're going to do something like this, I'd much prefer a sane
> output format over something that's easily parseble by just one thing.
>
>
Does "by just one thing" mean that the ioctl() for format setting
should not be allowed? I have to admit that this patch adds lots of
ugly if and switch statements. If I have to choose just one style
in order to forbid increasing expressions, I'd like to choose
S-expression because it is easy to parse by any language.
next prev parent reply other threads:[~2011-02-28 23:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-22 15:28 [PATCH] perf lock: clean the options for perf record Hitoshi Mitake
2011-02-22 15:30 ` Hitoshi Mitake
2011-02-22 15:43 ` Peter Zijlstra
2011-02-22 18:22 ` Frederic Weisbecker
2011-02-23 4:17 ` Hitoshi Mitake
2011-02-24 15:46 ` Hitoshi Mitake
2011-02-24 16:50 ` Frederic Weisbecker
2011-02-25 17:10 ` Hitoshi Mitake
2011-02-28 15:00 ` [PATCH] lockstat: export data in python expression Hitoshi Mitake
2011-02-28 18:07 ` Peter Zijlstra
2011-02-28 23:48 ` Hitoshi Mitake [this message]
2011-03-04 14:08 ` Steven Rostedt
2011-03-01 14:55 ` [PATCH] perf lock: clean the options for perf record Frederic Weisbecker
2011-03-04 9:41 ` Hitoshi Mitake
2011-03-04 13:56 ` Frederic Weisbecker
2011-03-04 13:58 ` Peter Zijlstra
2011-03-04 14:21 ` Frederic Weisbecker
2011-03-09 16:41 ` Hitoshi Mitake
2011-03-04 14:37 ` Steven Rostedt
2011-03-04 14:41 ` Frederic Weisbecker
2011-03-05 17:20 ` Hitoshi Mitake
2011-03-05 17:14 ` Hitoshi Mitake
2011-02-22 18:09 ` Frederic Weisbecker
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=4D6C3461.8010109@dcl.info.waseda.ac.jp \
--to=mitake@dcl.info.waseda.ac.jp \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=fweisbec@gmail.com \
--cc=h.mitake@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=rostedt@goodmis.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 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®