From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Eric Dumazet <eric.dumazet@gmail.com>
Subject: Re: seq_put_decimal_ull() et al
Date: Mon, 19 Mar 2012 09:29:37 +0900 [thread overview]
Message-ID: <4F667DF1.3090109@jp.fujitsu.com> (raw)
In-Reply-To: <CACVxJT9mkX+7+hFrbt2rNCjUH9Y=t2AtGaXqcGfMh6x5WwMjmw@mail.gmail.com>
(2012/03/16 20:16), Alexey Dobriyan wrote:
> On Wed, Mar 14, 2012 at 5:08 AM, KAMEZAWA Hiroyuki
> <kamezawa.hiroyu@jp.fujitsu.com> wrote:
>> On Wed, 14 Mar 2012 09:31:56 +0900
>> KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:
>>
>>> On Tue, 13 Mar 2012 15:35:54 +0200
>>> Alexey Dobriyan <adobriyan@gmail.com> wrote:
>>>
>>>>> Subject: + procfs-add-num_to_str-to-speed-up-proc-stat-fix-2.patch added to -mm tree
>>>>
>>>> I think the fix is to create proper binary interface for exporting
>>>> interrupt counts.
>>>> Programs can parse raw data equally well if programming language is
>>>> even minimally reasonable
>>>> (POSIX shell may not qualify, though).
>>>
>>> Ok, please try with all tool-chain updates.
>>> procps, top, sar, and more ?
>>>
>
> Well, why not?
> We can tune print code or we can create maximally fast interface and forget.
>
Do you have an idea where to place it ?
/proc/stat_binary ?
/proc/binary/stat ?
Hm, to parse /proc/stat binary format, the user has to know the format of the
kernel version.
Do we show a format file as
/proc/binary/stat_format and show
# cat /proc/binary/stat_format
=IHHHIHIQQQIHQQ...
as python's pack/unpack ? or
export the format via /usr/include/linux/proc_format.h ? as a structure ?
any better idea ?
Thanks,
-Kame
next prev parent reply other threads:[~2012-03-19 0:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-13 13:35 seq_put_decimal_ull() et al Alexey Dobriyan
2012-03-13 13:41 ` Alexey Dobriyan
2012-03-14 0:31 ` KAMEZAWA Hiroyuki
2012-03-14 2:08 ` KAMEZAWA Hiroyuki
2012-03-16 11:16 ` Alexey Dobriyan
2012-03-19 0:29 ` KAMEZAWA Hiroyuki [this message]
2012-03-19 12:53 ` Alexey Dobriyan
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=4F667DF1.3090109@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=eric.dumazet@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox