linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@suse.de>
To: David Milburn <dmilburn@redhat.com>
Cc: linux-scsi@vger.kernel.org, jeff@garzik.org, k.skarlatos@gmail.com
Subject: Re: [PATCH] mvsas: defer non-NCQ cmds when NCQ cmds are active
Date: Tue, 21 Sep 2010 15:51:14 -0500	[thread overview]
Message-ID: <1285102274.16440.132.camel@mulgrave.site> (raw)
In-Reply-To: <20100921191701.GA16726@dhcp-10-15-1-70.hsv.redhat.com>

On Tue, 2010-09-21 at 14:17 -0500, David Milburn wrote:
> Non-NCQ commands should run exclusively, ata_qc_issue warns when mixing
> non-NCQ and NCQ commands.
> 
> Signed-off-by: David Milburn <dmilburn@redhat.com>
> Reported-by: Konstantinos Skarlatos <k.skarlatos@gmail.com>
> ---
>  drivers/scsi/libsas/sas_ata.c |    1 +
>  1 files changed, 1 insertions(+), 0 deletions(-)
> 
> diff --git a/drivers/scsi/libsas/sas_ata.c b/drivers/scsi/libsas/sas_ata.c
> index 042153c..ddbade7 100644
> --- a/drivers/scsi/libsas/sas_ata.c
> +++ b/drivers/scsi/libsas/sas_ata.c
> @@ -347,6 +347,7 @@ static int sas_ata_scr_read(struct ata_link *link, unsigned int sc_reg_in,
>  static struct ata_port_operations sas_sata_ops = {
>  	.phy_reset		= sas_ata_phy_reset,
>  	.post_internal_cmd	= sas_ata_post_internal,
> +	.qc_defer               = ata_std_qc_defer,

What does this do on the card that doesn't need it: the aic94xx?  That
one takes in a pipeline of commands and takes responsibility for getting
the issue right.  Something like this throttles the pipeline higher than
the aic94xx is expecting.  However, as long as it's not too much of a
performance problem, I don't mind applying it.

James



  parent reply	other threads:[~2010-09-21 20:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-21 19:17 [PATCH] mvsas: defer non-NCQ cmds when NCQ cmds are active David Milburn
2010-09-21 19:41 ` Jeff Garzik
2010-09-21 20:51 ` James Bottomley [this message]
2010-09-22  0:24   ` David Milburn

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=1285102274.16440.132.camel@mulgrave.site \
    --to=james.bottomley@suse.de \
    --cc=dmilburn@redhat.com \
    --cc=jeff@garzik.org \
    --cc=k.skarlatos@gmail.com \
    --cc=linux-scsi@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 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).