From: Willy Tarreau <willy@w.ods.org>
To: Andreas Haumer <andreas@xss.co.at>
Cc: arjanv@redhat.com, "Miller, Mike (OS Dev)" <mike.miller@hp.com>,
Christoph Hellwig <hch@infradead.org>,
mikem@beardog.cca.cpqcorp.net, marcelo.tosatti@cyclades.com,
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: Fri, 1 Oct 2004 07:21:46 +0200 [thread overview]
Message-ID: <20041001052146.GD721@alpha.home.local> (raw)
In-Reply-To: <415AE9CF.40008@xss.co.at>
On Wed, Sep 29, 2004 at 06:58:55PM +0200, Andreas Haumer wrote:
> The majority of _our_ customers are using 2.4.x kernels
> (x beeing in the range from 19 to 28pre3) and it looks like
> it will stay that for quite a while...
I second this. The only one of our customers who tried 2.6 went back to
2.4 because of poor network performance, scheduling problems and stability
issues.
> PS: I know this is somewhat off topic, but I just want to raise
> my voice if I get the impression kernel developers forget about
> the "real world outside". I will shut up in a moment! Thank you!
Very true. You just have to read any 2.6 changelog to understand that
it *is* a development kernel ! The difference between 2.5 and 2.6 is
that the test platform now is larger and includes production systems.
Willy
next prev parent reply other threads:[~2004-10-01 5:24 UTC|newest]
Thread overview: 13+ 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:43 ` Arjan van de Ven
2004-09-29 16:58 ` Andreas Haumer
2004-10-01 5:21 ` Willy Tarreau [this message]
2004-09-29 17:20 ` mikem
2004-10-01 5:33 ` Willy Tarreau
2004-09-29 20:35 ` Marcelo Tosatti
-- strict thread matches above, loose matches on Subject: below --
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 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=20041001052146.GD721@alpha.home.local \
--to=willy@w.ods.org \
--cc=andreas@xss.co.at \
--cc=arjanv@redhat.com \
--cc=brian.b@hp.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--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 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).