mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andries Brouwer <aebr@win.tue.nl>
To: Christoph Hellwig <hch@lst.de>, Kurt Garloff <kurt@garloff.de>,
	Linux kernel list <linux-kernel@vger.kernel.org>,
	Marcelo Tosatti <marcelo@conectiva.com.br>
Subject: Re: [PATCH] conditionally re-enable per-disk stats, convert to seq_file
Date: Thu, 8 Aug 2002 00:59:39 +0200	[thread overview]
Message-ID: <20020807225939.GA509@win.tue.nl> (raw)
In-Reply-To: <20020808003325.A14578@lst.de>

On Thu, Aug 08, 2002 at 12:33:25AM +0200, Christoph Hellwig wrote:
> On Wed, Aug 07, 2002 at 11:18:56PM +0200, Andries Brouwer wrote:
> > But why in /proc/partitions ?
> > Maybe /proc/partitions can go away eventually with all info available
> > under driverfs or so. But for the time being, /proc/partitions is used,
> > and some changes are planned to make identification of the devices
> > involved easier.
> > It is really ugly to stuff a lot of garbage into a file just because
> > it happens to exist already. If you want disk statistics, why not
> > put it in /proc/diskstatistics?
> 
> Because it's where existing tools expect it.  I agree with you that we
> want a nicer interface for 2.6, but give the userbase some time to
> prepare for a new interface.

You create a mess in the official kernel because your user space tools
are broken? And it is easier to patch the kernel than to fix them,
even though you'll have to fix them eventually?
And fixing these tools consists of replacing one filename?

  reply	other threads:[~2002-08-07 22:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-06 14:08 Christoph Hellwig
2002-08-07 21:02 ` Kurt Garloff
2002-08-07 21:18   ` Andries Brouwer
2002-08-07 22:33     ` Christoph Hellwig
2002-08-07 22:59       ` Andries Brouwer [this message]
2002-08-07 23:10     ` Randy.Dunlap
2002-08-07 23:18       ` Christoph Hellwig

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=20020807225939.GA509@win.tue.nl \
    --to=aebr@win.tue.nl \
    --cc=hch@lst.de \
    --cc=kurt@garloff.de \
    --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

all inboxes | Powered by JetHome®