From: James Bottomley <James.Bottomley@steeleye.com>
To: "Justin T. Gibbs" <gibbs@scsiguy.com>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>,
Linus Torvalds <torvalds@transmeta.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Marcelo Tosatti <marcelo@conectiva.com.br>,
Andrew Morton <akpm@osdl.org>
Subject: Re: Aic7x_x_x 6.3.4 && Aic79xx 2.0.5 Updates
Date: 27 Dec 2003 09:52:43 -0600 [thread overview]
Message-ID: <1072540364.2030.41.camel@mulgrave> (raw)
In-Reply-To: <2906490000.1072499170@aslan.scsiguy.com>
On Fri, 2003-12-26 at 22:26, Justin T. Gibbs wrote:
> You're telling me that fail-over for a multi-controller external RAID box
> connected to a single SCSI controller will occur at a higher level? The
> fail-over has already occurred by the time the HBA see the timeout. This
> means that completion of recovery is the only impediment to completing the
> fail-over.
The usual architecture of a multiple controller RAID box is no
SPOF...Therefore *two* or more SCSI cards...local in card attempts at
recovery only delays eventual failover.
> I've already written one OpenSource SCSI layer, I think I've contributed
> more than enough in that particular area. Back in late 2000 and early 2001,
> I voiced my opinions, based on that experience, on how Linux should improve
> its SCSI subsystem. After 3 years of waiting for improvement in the
> error recovery semantics of Linux, I had to do something to satisfy customer
> complaints on error recovery. I still don't see things improving in
> this area of Linux and I'm not about to *break* the driver until there is
> a viable alternative.
This is open source...areas which cause problems for many people get
fixed (OK, often many times). Areas that only annoy one person don't
get fixed just by expressing that annoyance.
> I'm sorry you feel that way. I suppose I will just have to continue
> to point distributors and users of this driver to my own patch sets since
> that seems to be the only viable alternative you've given me.
OK, I'll be sorry to see it happen, but if Adaptec formally wishes to
relinquish maintainership of the aic7xxx/aic79xx drivers and develop
their own fork of the kernel, that is, of course, their right under the
GPL. If this is what you want to do, could you send the list a note to
that effect so that I can begin looking for a new maintainer now.
James
next prev parent reply other threads:[~2003-12-27 15:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-03 23:51 (unknown) Justin T. Gibbs
2003-06-03 23:58 ` Marc-Christian Petersen
2003-06-04 1:34 ` Aic7x_x_x 6.2.36 && Aic79xx 1.3.10 Updates Justin T. Gibbs
2003-12-24 16:58 ` Aic7x_x_x 6.3.4 && Aic79xx 2.0.5 Updates Justin T. Gibbs
2003-12-24 17:50 ` James Bottomley
[not found] ` <2148850000.1072292121@aslan.scsiguy.com>
2003-12-24 19:05 ` James Bottomley
2003-12-25 4:31 ` Justin T. Gibbs
2003-12-26 18:36 ` James Bottomley
2003-12-27 0:13 ` Justin T. Gibbs
2003-12-27 3:20 ` James Bottomley
2003-12-27 4:26 ` Justin T. Gibbs
2003-12-27 6:08 ` Jeff Garzik
2003-12-27 15:11 ` Alan Cox
2003-12-27 15:47 ` Justin T. Gibbs
2003-12-27 15:52 ` James Bottomley [this message]
2003-12-27 15:17 ` Alan Cox
2003-12-27 15:54 ` James Bottomley
2003-12-27 23:55 ` Alan Cox
2003-12-27 16:02 ` Justin T. Gibbs
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=1072540364.2030.41.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gibbs@scsiguy.com \
--cc=linux-scsi@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=torvalds@transmeta.com \
/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