From: James Bottomley <James.Bottomley@steeleye.com>
To: Xose Vazquez Perez <xose@wanadoo.es>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Tosatti <marcelo.tosatti@cyclades.com>,
linux-scsi <linux-scsi@vger.kernel.org>,
"Justin T. Gibbs" <gibbs@scsiguy.com>
Subject: Re: AIC7xxx kernel problem with 2.4.2[234] kernels
Date: 19 Jan 2004 12:21:50 -0500 [thread overview]
Message-ID: <1074532919.1895.32.camel@mulgrave> (raw)
In-Reply-To: <400BDC85.8040907@wanadoo.es>
On Mon, 2004-01-19 at 08:32, Xose Vazquez Perez wrote:
> It looks like the _kernel_ driver is going to be without a maintainer
> unless somebody works on it, porting ADAPTEC fixes/features to the kernel driver.
As I told you in private email, this is *not* the way I see it. At the
moment, Ataptec is the maintainer of that driver unless they choose
formally to relinquish it.
There is a glimmering of a resolution of the problem in an early
notification API for command timeouts.
Although throwing away successful completions when error recovery is in
progress isn't a bug (scsi commands are either idempotent or non
retryable), it's certainly not ideal. I'm thinking about a better
framework where we would quiesce the device but pull back from
activating the eh thread if all commands return. This would also fix
the tag starvation issue that many drivers tackle independently too.
James
next prev parent reply other threads:[~2004-01-19 17:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-19 13:32 AIC7xxx kernel problem with 2.4.2[234] kernels Xose Vazquez Perez
2004-01-19 17:21 ` James Bottomley [this message]
2004-01-19 18:38 ` Justin T. Gibbs
2004-01-20 0:50 ` James Bottomley
2004-01-20 2:02 ` Justin T. Gibbs
2004-01-20 4:45 ` James Bottomley
2004-01-20 5:43 ` Justin T. Gibbs
2004-01-22 5:14 ` James Bottomley
2004-01-20 11:24 ` Chiaki
2004-01-20 7:15 ` Linus Torvalds
2004-01-20 8:30 ` Andre Hedrick
2004-01-21 20:37 ` Guennadi Liakhovetski
-- strict thread matches above, loose matches on Subject: below --
2004-01-16 21:43 Stephen Smoogen
2004-01-16 22:39 ` Justin T. Gibbs
2004-01-16 22:59 ` Stephen Smoogen
2004-01-21 19:59 ` Stephen Smoogen
2004-02-18 19:42 ` Stephen Smoogen
2004-01-16 23:17 ` Marcelo Tosatti
2004-01-18 1:11 ` Marcelo Tosatti
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=1074532919.1895.32.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=gibbs@scsiguy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=xose@wanadoo.es \
/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.