From: Mikael Pettersson <mikpe@it.uu.se>
To: jeff@garzik.org, w@1wt.eu
Cc: htejun@gmail.com, linux-kernel@vger.kernel.org, tmmlkml@gmail.com
Subject: Re: 2.4.x libata resync
Date: Wed, 20 Sep 2006 16:52:35 +0200 (MEST) [thread overview]
Message-ID: <200609201452.k8KEqZBp014384@alkaid.it.uu.se> (raw)
On Sat, 16 Sep 2006 18:05:20 +0200, Willy Tarreau wrote:
>> >>Oh there are tons of SATA bug fixes that 2.4.x is missing. One of the
>> >>biggest is the completely crappy exception handling. If a SATA device
>> >>is unplugged or spazzes out, the system may or may not recover.
>> >
>> >Already encountered on sata_nv in a sun x2100 :-)
>> >
>> >Jeff, I did not want to blindly merge patches from 2.6 to 2.4, but if
>> >you point me to a few ones you consider important, I'm willing to merge
>> >them.
>>
>> As was hinted, it's not that easy, otherwise someone would have done it
>> by now. libata bug fixes require infrastructure that isn't present on
>> 2.4. The overall codebase is just too different to easily pull out
>> select bug fixes.
>
>Of course for those. I was thinking about those which just change one
>register or things like this that I cannot identify the expected effect.
>If you agree, I'll enumerate the ones I've already noticed so that you
>just have to say yes/no/unknown on them. Don't worry, I don't want to
>spend lots of hours on this, since as I said, I do not receive any
>feedback from SATA users on 2.4 (neither positive nor negative).
Here's some positive feedback: My leafnode News server
(a 440BX chipset mobo with a Tualatin PIII-S) has been using
Promise SATA PCI cards (currently a SATA300 TX2plus) for its
disk storage since the SATA update patch was made available
for 2.4.29. It's been fast and reliable the entire time.
/Mikael
next reply other threads:[~2006-09-20 14:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-20 14:52 Mikael Pettersson [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-09-16 5:14 Tom Mortensen
2006-09-16 5:37 ` Willy Tarreau
2006-09-16 6:27 ` Tejun Heo
2006-09-16 6:38 ` Willy Tarreau
2006-09-16 15:49 ` Jeff Garzik
2006-09-16 15:51 ` Willy Tarreau
2006-09-16 16:07 ` Jeff Garzik
2006-09-16 16:05 ` Willy Tarreau
2006-09-16 16:27 ` Jeff Garzik
2006-09-16 16:22 ` Willy Tarreau
2006-09-16 6:47 ` Tom Mortensen
2006-09-16 6:18 ` Jeff Garzik
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=200609201452.k8KEqZBp014384@alkaid.it.uu.se \
--to=mikpe@it.uu.se \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tmmlkml@gmail.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®