From: Marcelo Tosatti <marcelo@conectiva.com.br>
To: Christoph Hellwig <hch@infradead.org>
Cc: Andries.Brouwer@cwi.nl, Alan Cox <alan@lxorguk.ukuu.org.uk>,
hpa@zytor.com, lkml <linux-kernel@vger.kernel.org>
Subject: Re: IO stats in /proc/partitions
Date: Thu, 23 May 2002 17:27:13 -0300 (BRT) [thread overview]
Message-ID: <Pine.LNX.4.21.0205231723450.3295-100000@freak.distro.conectiva> (raw)
In-Reply-To: <20020516085022.B14643@infradead.org>
On Thu, 16 May 2002, Christoph Hellwig wrote:
> On Wed, May 15, 2002 at 06:39:03PM -0300, Marcelo Tosatti wrote:
> > > 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.
> > >
> > > Please keep these disk statistics apart from /proc/partitions.
> >
> > The change can possibly break userlevel tools which were working with
> > 2.4.18.
> >
> > Christoph, please create a /proc/diskstatistics file or something like
> > that and send me a patch.
>
> I rather send a complete backout patch for mainline instead. This format
> has been used by the vendor (Red Hat, SuSE, etc..) kernels since 2.2 ages
> and is used (if present) by the stock performance tools for linux
> (i.e. syststat package, iostats
Look, I just do not want to break some apps which read /proc/partitions.
Thats it.
Look, changing the userlevel apps to at least know about the new format is
not hard. And you can do that over time.
Do you see why I think /proc/whatever-else is interesting ?
next prev parent reply other threads:[~2002-05-23 21:25 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
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 [this message]
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=Pine.LNX.4.21.0205231723450.3295-100000@freak.distro.conectiva \
--to=marcelo@conectiva.com.br \
--cc=Andries.Brouwer@cwi.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hch@infradead.org \
--cc=hpa@zytor.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;
as well as URLs for NNTP newsgroup(s).