From: Tejun Heo <htejun@gmail.com>
To: Mark Lord <lkml@rtr.ca>
Cc: axboe@suse.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] blk: fix possible queue stall in blk_do_ordered
Date: Fri, 13 Jan 2006 01:26:36 +0900 [thread overview]
Message-ID: <43C6833C.1000704@gmail.com> (raw)
In-Reply-To: <43C67F20.30300@rtr.ca>
Mark Lord wrote:
> Tejun Heo wrote:
>
>> Previously, if a fs request which was being drained failed and got
>> requeued, blk_do_ordered() didn't allow it to be reissued, which
>> causes queue stall. This patch makes blk_do_ordered() use the
>> sequence of each request to determine whether a request can be issued
>> or not. This fixes the bug and simplifies code.
>
>
> What kernel(s) is this against? The patch seems to fail on 2.6.15.
>
> Thanks
It's against v2.6.15-mm2. It's sort of a follow-up patch for the following.
http://marc.theaimsgroup.com/?l=linux-kernel&m=113707430626490&w=2
--
tejun
prev parent reply other threads:[~2006-01-12 16:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-12 15:29 [PATCH] blk: fix possible queue stall in blk_do_ordered Tejun Heo
2006-01-12 16:09 ` Mark Lord
2006-01-12 16:26 ` Tejun Heo [this message]
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=43C6833C.1000704@gmail.com \
--to=htejun@gmail.com \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
/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