From: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
To: Andrew Morton <akpm@digeo.com>, Rick Lindsley <ricklind@us.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] sard changes for 2.5.34
Date: Thu, 12 Sep 2002 21:32:26 -0200 [thread overview]
Message-ID: <200209121837.g8CIbIp06737@Port.imtp.ilyichevsk.odessa.ua> (raw)
In-Reply-To: <3D804036.4C000672@digeo.com>
On 12 September 2002 05:20, Andrew Morton wrote:
> > Lastly, a bit of a philosophical question. /proc/stat and (with this
> > patch) /proc/diskstats provide some of the same information. Should
> >
> > a) all of it appear in /proc/stat?
> >
> > b) all of it appear in /proc/diskstats?
> >
> > c) keep the current (limited) info in /proc/stat (for backward
> > compatibility) and introduce the expanded info in
> > /proc/diskstats?
> >
> > My preference is b, but I'm open to other opinions.
>
> b). Let's get the kernel right and change userspace to follow. We have
> another accounting patch which breaks top(1), so Rik has fixed it (and
> is feeding the fixes upstream).
Erm... Some of /proc/stat data has no relations to disks, namely CPU counts.
It would be strange to have CPU stats in /proc/diskstats...
--
vda
next prev parent reply other threads:[~2002-09-12 18:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-12 2:10 [RFC][PATCH] sard changes for 2.5.34 Rick Lindsley
2002-09-12 2:42 ` Andrew Morton
2002-09-12 2:50 ` Rik van Riel
2002-09-12 6:40 ` Rick Lindsley
2002-09-12 7:20 ` Andrew Morton
2002-09-12 9:18 ` Rick Lindsley
2002-09-12 10:01 ` Alexander Viro
2002-09-12 10:33 ` Rick Lindsley
2002-09-12 19:42 ` Andrew Morton
2002-09-12 20:38 ` Rik van Riel
2002-09-12 16:16 ` Rik van Riel
2002-09-12 16:48 ` Andrew Morton
2002-09-12 23:32 ` Denis Vlasenko [this message]
2002-09-12 18:49 ` Andrew Morton
2002-09-12 19:50 ` Rick Lindsley
2002-09-13 11:39 Dipankar Sarma
2002-09-14 18:57 Lev Makhlis
2002-09-18 17:54 ` Randy.Dunlap
2002-09-18 19:43 ` Lev Makhlis
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=200209121837.g8CIbIp06737@Port.imtp.ilyichevsk.odessa.ua \
--to=vda@port.imtp.ilyichevsk.odessa.ua \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ricklind@us.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).