From: "H. Peter Anvin" <hpa@zytor.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Andries.Brouwer@cwi.nl, linux-kernel@vger.kernel.org,
marcelo@conectiva.com.br
Subject: Re: IO stats in /proc/partitions
Date: Sat, 04 May 2002 15:46:34 -0700 [thread overview]
Message-ID: <3CD464CA.8010309@zytor.com> (raw)
In-Reply-To: <E1748Oo-0000Ub-00@the-village.bc.nu>
Alan Cox wrote:
>>Earlier I noticed that RedHat did put some statistics in
>>/proc/partitions. That was bad, but I assumed that it was
>>their laziness, being too busy to do a proper job.
>
> It was put there in the 2.2 era after discussion with various folks. Its
> been in most vendor kernels for about four years.
>
>>On the other hand, disk statistics should not be in
>>/proc/partitions. They should be in /proc/diskstatistics.
>>I see a heading today "rio rmerge rsect ruse wio wmerge"
>>"wsect wuse running use aveq". No doubt next year we'll
>>want different statistics. So /proc/diskstatistics should
>>start with a header line including a version field.
>
> The stats have been unchanged for years too. As to version lines
> why ? This is lets mke /proc XML hell again
>
>>Please keep these disk statistics apart from /proc/partitions.
>
> It has to contain each partiiton anyway.
If we're going to add stuff to /proc/partitions, I'd really like to see
it contain: a) parent device, and b) offset.
-hpa
next prev parent reply other threads:[~2002-05-04 22:47 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-04 19:59 IO stats in /proc/partitions Andries.Brouwer
2002-05-04 20:35 ` M. Edward Borasky
2002-05-04 21:25 ` Mark Hahn
2002-05-05 1:04 ` M. Edward (Ed) Borasky
2002-05-06 14:04 ` Jakob Østergaard
2002-05-04 21:35 ` Tomas Szepe
2002-05-05 1:08 ` M. Edward (Ed) Borasky
2002-05-05 1:18 ` Mike Fedyk
2002-05-05 16:55 ` Denis Vlasenko
2002-05-05 18:10 ` M. Edward (Ed) Borasky
2002-05-05 23:51 ` Thomas Zimmerman
2002-05-04 22:53 ` Alan Cox
2002-05-04 22:46 ` H. Peter Anvin [this message]
2002-05-15 21:39 ` Marcelo Tosatti
2002-05-15 23:18 ` Miquel van Smoorenburg
2002-05-16 0:30 ` Alan Cox
2002-05-20 18:19 ` Bill Davidsen
2002-05-21 0:36 ` Guest section DW
2002-05-21 13:11 ` Alan Cox
2002-05-16 7:50 ` Christoph Hellwig
2002-05-23 20:27 ` Marcelo Tosatti
2002-05-24 9:56 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2002-05-05 1:38 Nivedita Singhvi
2002-03-12 15:34 Jean-Eric Cuendet
2002-03-12 21:51 ` H. Peter Anvin
2002-03-12 22:48 ` Anton Altaparmakov
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=3CD464CA.8010309@zytor.com \
--to=hpa@zytor.com \
--cc=Andries.Brouwer@cwi.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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