linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Miquel van Smoorenburg" <miquels@cistron.nl>
To: linux-kernel@vger.kernel.org
Subject: Re: IO stats in /proc/partitions
Date: Wed, 15 May 2002 23:18:34 +0000 (UTC)	[thread overview]
Message-ID: <abuqca$ipn$2@ncc1701.cistron.net> (raw)
In-Reply-To: <UTC200205041959.g44JxQa20044.aeb@smtp.cwi.nl> <Pine.LNX.4.21.0205151838001.21222-100000@freak.distro.conectiva>

In article <Pine.LNX.4.21.0205151838001.21222-100000@freak.distro.conectiva>,
Marcelo Tosatti  <marcelo@conectiva.com.br> wrote:
>On Sat, 4 May 2002 Andries.Brouwer@cwi.nl wrote:
>
>> However, I see that these days the pollution of /proc/partitions
>> is becoming official - it is part of patch-2.4.19-pre7.
>> I strongly object, and hope it is not too late to revert this.
>> 
>The change can possibly break userlevel tools which were working with
>2.4.18.

Perhaps, but I had the opposite experience. I noticed by accident
that iostat (as included in Debian) suddenly had working extended
statistics. So there are *certainly* tools that get fixed by
2.4.19-pre7. I was pleasantly surprised.

>Christoph, please create a /proc/diskstatistics file or something like
>that and send me a patch.

Bummer, I'm using Debian, and iostat is in woody (frozen, about to
be released) - that means Debian users will have to wait to the
next release, another two years perhaps, before iostat gets working.

Why not keep it as it is, it's probably not going to break
anything as debian and redhat tools already know about this
apparently. 2.5 is about new features, 2.4 is about stability
and, though some might oppose, folding in stable patches that
have been in vendor kernels for months or years.

Mike.
-- 
"Insanity -- a perfectly rational adjustment to an insane world."
  - R.D. Lang


  reply	other threads:[~2002-05-15 23:18 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 [this message]
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='abuqca$ipn$2@ncc1701.cistron.net' \
    --to=miquels@cistron.nl \
    --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).