From: Jeff Garzik <jgarzik@pobox.com>
To: Gwendal Grignou <gwendal@google.com>
Cc: mlord@pobox.com, linux-ide@vger.kernel.org
Subject: Re: [PATCH 1/1] sata_mv: Prevent PIO commands to be defered too long if traffic in progress.
Date: Fri, 16 Oct 2009 06:26:22 -0400 [thread overview]
Message-ID: <4AD84A4E.1090200@pobox.com> (raw)
In-Reply-To: <1255387440-13313-2-git-send-email-gwendal@google.com>
On 10/12/2009 06:44 PM, Gwendal Grignou wrote:
> Use excl_link when non NCQ commands are defered, to be sure they are processed
> as soon as outstanding commands are completed. It prevents some commands to be
> defered indifinitely when using a port multiplier.
>
> Signed-off-by: Gwendal Grignou<gwendal@google.com>
> ---
> drivers/ata/sata_mv.c | 29 +++++++++++++++++++++++++++--
> 1 files changed, 27 insertions(+), 2 deletions(-)
applied
prev parent reply other threads:[~2009-10-16 10:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 22:43 [PATCH 0/1] sata_mv: Prevent PIO commands to be defered too long if traffic in progress Gwendal Grignou
2009-10-12 22:44 ` [PATCH 1/1] " Gwendal Grignou
2009-10-13 1:44 ` Grant Grundler
2009-10-14 12:35 ` Mark Lord
2009-10-14 12:38 ` Jeff Garzik
2009-10-16 10:26 ` Jeff Garzik [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=4AD84A4E.1090200@pobox.com \
--to=jgarzik@pobox.com \
--cc=gwendal@google.com \
--cc=linux-ide@vger.kernel.org \
--cc=mlord@pobox.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;
as well as URLs for NNTP newsgroup(s).