From: Jens Axboe <axboe@suse.de>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Linux Kernel Mailing List <Linux-Kernel@vger.kernel.org>
Subject: Re: [patch 2.6.15-rc2] blk: request poisoning
Date: Mon, 21 Nov 2005 08:33:58 +0100 [thread overview]
Message-ID: <20051121073357.GS25454@suse.de> (raw)
In-Reply-To: <438182E7.9080809@yahoo.com.au>
On Mon, Nov 21 2005, Nick Piggin wrote:
> This patch should make request poisoning more useful
> and more easily extendible in the block layer.
>
> Don't think I have hardware that will trigger a requeue,
> but otherwise it has been moderately tested. Comments?
I like the idea, but I'm a little worried that it actually introduces
more problems than it solves. See the mail from yesterday for instance,
perfectly fine code but 'as' poisoning triggered.
And the merging bits already look really ugly :/
So I guess my question is, did this code ever find any driver problems?
--
Jens Axboe
next prev parent reply other threads:[~2005-11-21 7:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-21 8:18 [patch 2.6.15-rc2] blk: request poisoning Nick Piggin
2005-11-21 7:33 ` Jens Axboe [this message]
2005-11-21 8:48 ` Nick Piggin
2005-11-21 7:56 ` Jens Axboe
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=20051121073357.GS25454@suse.de \
--to=axboe@suse.de \
--cc=Linux-Kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
/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