All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: "Miller, Mike (OS Dev)" <mike.miller@hp.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	mikem@beardog.cca.cpqcorp.net, linux-kernel@vger.kernel.org,
	linux-scsi@vger.kernel.org, "Baker,
	Brian (ISS - Houston)" <brian.b@hp.com>
Subject: Re: patch so cciss stats are collected in /proc/stat
Date: Wed, 29 Sep 2004 17:35:48 -0300	[thread overview]
Message-ID: <20040929203548.GA19037@logos.cnet> (raw)
In-Reply-To: <D4CFB69C345C394284E4B78B876C1CF107DBFE0B@cceexc23.americas.cpqcorp.net>

On Wed, Sep 29, 2004 at 11:29:59AM -0500, Miller, Mike (OS Dev) wrote:
> 
> > On Wed, Sep 29, 2004 at 11:13:45AM -0500, mike.miller@hp.com wrote:
> > > Currently cciss statistics are not collected in /proc/stat. 
> > This patch
> > > bumps DK_MAX_MAJOR to 111 to fix that. This has been a 
> > common complaint
> > > by customers wishing to gather info about cciss devices.
> > > Please consider this for inclusion. Applies to 2.4.28-pre3.
> > 
> > This patch has been reject about half a million times, why are people
> > submitting it again and again?
> 
> As I said in my mail, it's a customer driven issue. As long as customers rely on /proc/stat we'll keep trying. You can't tell a customer how he/she should be doing things on their systems.

Mike, 

I dont like the patch either.

If you can have the same statistics through /proc/partitions 
(do I get this right?) just tell that to users.


  parent reply	other threads:[~2004-09-29 22:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-29 16:29 patch so cciss stats are collected in /proc/stat Miller, Mike (OS Dev)
2004-09-29 16:29 ` Miller, Mike (OS Dev)
2004-09-29 16:43 ` Arjan van de Ven
2004-09-29 16:58   ` Andreas Haumer
2004-10-01  5:21     ` Willy Tarreau
2004-09-29 17:20   ` mikem
2004-10-01  5:33   ` Willy Tarreau
2004-09-29 20:35 ` Marcelo Tosatti [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-09-29 19:26 Miller, Mike (OS Dev)
2004-09-29 19:26 ` Miller, Mike (OS Dev)
2004-09-29 19:39 ` Neil Horman
2004-09-29 17:25 Miller, Mike (OS Dev)
2004-09-29 17:25 ` Miller, Mike (OS Dev)
2004-09-29 16:13 mike.miller
2004-09-29 16:19 ` Christoph Hellwig
2004-09-29 19:08 ` Neil Horman

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=20040929203548.GA19037@logos.cnet \
    --to=marcelo.tosatti@cyclades.com \
    --cc=brian.b@hp.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mike.miller@hp.com \
    --cc=mikem@beardog.cca.cpqcorp.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.