From: Tejun Heo <tj@kernel.org>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: "David S. Miller" <davem@davemloft.net>, linux-ide@vger.kernel.org
Subject: Re: ide: Requeue request after DMA timeout
Date: Thu, 01 Apr 2010 12:04:44 +0900 [thread overview]
Message-ID: <4BB40D4C.7010204@kernel.org> (raw)
In-Reply-To: <20100331061731.GA11480@gondor.apana.org.au>
Hello, Herbert.
On 03/31/2010 03:17 PM, Herbert Xu wrote:
> commit 8f6205cd572fece673da0255d74843680f67f879
> Author: Tejun Heo <tj@kernel.org>
> Date: Fri May 8 11:53:59 2009 +0900
>
> ide: dequeue in-flight request
>
> The problem is that the function ide_dma_timeout_retry does not
> requeue the current request, causing one request to be lost for
> each DMA timeout.
Hmmm....
> diff --git a/drivers/ide/ide-dma.c b/drivers/ide/ide-dma.c
> index ee58c88..62a257f 100644
> --- a/drivers/ide/ide-dma.c
> +++ b/drivers/ide/ide-dma.c
> @@ -492,6 +492,7 @@ ide_startstop_t ide_dma_timeout_retry(ide_drive_t *drive, int error)
> if (rq) {
> hwif->rq = NULL;
> rq->errors = 0;
> + ide_requeue_request(drive, rq);
> }
> return ret;
> }
Hmmm... ide_dma_timeout_retry() is called from ide_timer_expiry() if
!hwif->polling. The former returns ide_stopped if the current request
processing should be stopped, in which case ide_timer_expiry() calls
plug_device to 1 which makes it call ide_requeue_and_plug() at the end
of the function. Does the above change make the request to be
requeued twice?
Thanks.
--
tejun
next prev parent reply other threads:[~2010-04-01 3:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-31 6:17 ide: Requeue request after DMA timeout Herbert Xu
2010-03-31 6:20 ` ide: Must hold queue lock when requeueing Herbert Xu
2010-04-01 3:06 ` Tejun Heo
2010-04-01 6:11 ` v2: ide: Requeue request after DMA timeout Herbert Xu
2010-04-01 6:13 ` v2: ide: Must hold queue lock when requeueing Herbert Xu
2010-04-01 8:31 ` David Miller
2010-04-01 8:31 ` v2: ide: Requeue request after DMA timeout David Miller
2010-04-01 2:34 ` David Miller
2010-04-01 3:05 ` Tejun Heo
2010-04-01 3:04 ` Tejun Heo [this message]
2010-04-01 4:32 ` Herbert Xu
2010-04-01 4:56 ` Tejun Heo
2010-04-01 5:54 ` Herbert Xu
2010-04-01 6:25 ` Tejun Heo
2010-04-01 6:32 ` Herbert Xu
2010-04-01 6:37 ` Tejun Heo
2010-04-01 7:54 ` Herbert Xu
2010-04-01 8:26 ` Tejun Heo
2010-04-01 8:27 ` David Miller
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=4BB40D4C.7010204@kernel.org \
--to=tj@kernel.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-ide@vger.kernel.org \
/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.