From: Alexey Dobriyan <adobriyan@gmail.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Hiroyuki Kamezawa <kamezawa.hiroyuki@gmail.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Ulrich Drepper <drepper@gmail.com>
Subject: Re: [RFC] [PATCH 1/2] binary stream format for /proc/stat
Date: Sun, 1 Apr 2012 13:30:16 +0300 [thread overview]
Message-ID: <20120401103015.GA3231@p183.telecom.by> (raw)
In-Reply-To: <alpine.LNX.2.01.1203312329500.16267@frira.zrqbmnf.qr>
On Sat, Mar 31, 2012 at 11:36:15PM +0200, Jan Engelhardt wrote:
>
> On Saturday 2012-03-31 23:23, Hiroyuki Kamezawa wrote:
> >>
> >> Rather than adding more obscure formats and fields to /proc(/N)/stat, we
> >> should pursue descriptive lines like in /proc/N/status.
> >> Or, if so desired, sysfs-style splitted attributes where the filename
> >> takes on the description.
> >
> >Yes, I like format like /proc/N/status , /proc/meminfo...which is
> >readable to me.
> >But when I wrote this patch, I didn't want to break current format.
> >
> >My concern on sysfs-style one data per a file is that it will add many
> >open/close and making top/ps/sar slow.
>
> Or you go netlink. That gives you a binary format.
And one more system call to acquire necessary data.
next prev parent reply other threads:[~2012-04-01 10:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 8:53 [RFC] [PATCH 1/2] binary stream format for /proc/stat KAMEZAWA Hiroyuki
2012-03-27 8:55 ` [RFC] [PATCH 2/2] add /proc/stat.bin KAMEZAWA Hiroyuki
2012-03-27 10:45 ` [RFC] [PATCH 1/2] binary stream format for /proc/stat Alexey Dobriyan
2012-03-31 14:42 ` Jan Engelhardt
2012-03-31 21:23 ` Hiroyuki Kamezawa
2012-03-31 21:36 ` Jan Engelhardt
2012-03-31 22:02 ` Hiroyuki Kamezawa
2012-04-01 10:30 ` Alexey Dobriyan [this message]
2012-03-31 19:47 ` Ulrich Drepper
2012-03-31 21:24 ` Hiroyuki Kamezawa
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=20120401103015.GA3231@p183.telecom.by \
--to=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=drepper@gmail.com \
--cc=jengelh@medozas.de \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kamezawa.hiroyuki@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