mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Gerd v. Egidy" <gerd.von.egidy@intra2net.com>
To: Willy Tarreau <w@1wt.eu>
Cc: Adrian Bunk <bunk@stusta.de>, Mikael Pettersson <mikpe@csd.uu.se>,
	Andreas Steinmetz <ast@domdv.de>,
	Arjan van de Ven <arjan@infradead.org>,
	linux-kernel@vger.kernel.org, mtosatti@redhat.com
Subject: Re: Linux 2.4.34-pre1
Date: Fri, 18 Aug 2006 01:41:19 +0200	[thread overview]
Message-ID: <200608180141.20040.gerd.von.egidy@intra2net.com> (raw)
In-Reply-To: <20060817204307.GA17391@1wt.eu>

Hi Willy,

first thank you for continuing work for 2.4, our company still relies on it 
for a lot of machines.

> By this time, those people obviously know that they will have more
> and more problems getting 2.4 to run reliably on fresh new hardware.

Yes, we've already experienced problems with new hw. We could solve most of 
the stuff with some vendor supplied patches. But now we got performance 
problems with ICH7 SATA performance: a disk does only about 11MB/s on 2.4 
with all 2.4 patches from Jeff applied while we get about 40MB/s on 2.6.16. 
Backporting the libata changes done between 2.6.15 (I think that is about the 
same codebase as the current 2.4 stuff) and 2.6.16 seems like a big task.

So my question is: what is your policy on new or enhanced drivers (not just 
new pciids)?

Kind regards,

Gerd

  reply	other threads:[~2006-08-17 23:41 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-16 22:36 Willy Tarreau
2006-08-16 23:54 ` Adrian Bunk
2006-08-17  5:16   ` Willy Tarreau
2006-08-17  6:48     ` Arjan van de Ven
2006-08-17  8:35       ` Andreas Steinmetz
2006-08-17  8:50         ` Mikael Pettersson
2006-08-17 12:48           ` Adrian Bunk
2006-08-17 20:43             ` Willy Tarreau
2006-08-17 23:41               ` Gerd v. Egidy [this message]
2006-08-18  4:40                 ` Willy Tarreau
2006-08-21  0:56               ` Adrian Bunk
2006-08-17  9:06         ` Adrian Bunk
2006-08-17  9:16           ` Andreas Steinmetz
2006-08-18 23:25             ` Adrian Bunk
2006-08-19  1:20               ` Grant Coady
2006-08-20 17:27                 ` Adrian Bunk
2006-08-19  4:45               ` Willy Tarreau
2006-08-21  0:35                 ` Adrian Bunk
2006-08-21  0:41                   ` Willy Tarreau
2006-08-21  1:07                     ` Adrian Bunk
2006-08-17  8:37       ` Willy Tarreau
2006-08-17  9:12 ` Thomas Voegtle
2006-08-18 22:48 ` Solar Designer
2006-08-18 23:11   ` Adrian Bunk
2006-08-18 23:27     ` Solar Designer
2006-08-17  7:57 Chris Rankin
2006-08-17  9:16 ` Thomas Backlund
2006-08-18  4:47   ` Willy Tarreau

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=200608180141.20040.gerd.von.egidy@intra2net.com \
    --to=gerd.von.egidy@intra2net.com \
    --cc=arjan@infradead.org \
    --cc=ast@domdv.de \
    --cc=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@csd.uu.se \
    --cc=mtosatti@redhat.com \
    --cc=w@1wt.eu \
    /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®