linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] SATA NCQ support
Date: Fri, 27 May 2005 09:56:21 +0200	[thread overview]
Message-ID: <20050527075621.GR1435@suse.de> (raw)
In-Reply-To: <20050527074712.GQ1435@suse.de>

On Fri, May 27 2005, Jens Axboe wrote:
> On Fri, May 27 2005, Jeff Garzik wrote:
> > Jens Axboe wrote:
> > >That is the typical case, ata_qc_new() succeeds but we cannot issue the
> > >command yet. So where do you want this logic placed? You cannot drop the
> > >host_lock in-between, as that could potentially change the situation.
> > 
> > ata_scsi_translate() in libata-scsi.c, in between the call to 
> > ata_scsi_qc_new() and ata_qc_issue().
> > 
> > something like:
> > 
> > 	if (ata_scsi_qc_new() fails ||
> > 	    (depth > 0 && ata_check_non_ncq_cmd()))
> > 		complete SCSI command with 'queue full'
> 
> That is an improvement for SCSI originated commands, I can drop
> ATA_QCFLAG_DEFER then. Will make that change. But what about
> ata_qc_issue() from other places? That is the ugly code, which will hit
> the waiting currently.

Actually, slight "problem" there as well... We need to translate the
SCSI command prior to making this decision, as we may get both NCQ and
non-NCQ commands from that path as well. For now I'll just make the
distinction that fs based SCSI requests are the only NCQ candidates, ok?

-- 
Jens Axboe


  reply	other threads:[~2005-05-27  7:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-27  7:03 [PATCH] SATA NCQ support Jens Axboe
2005-05-27  7:22 ` Jeff Garzik
2005-05-27  7:30   ` Jens Axboe
2005-05-27  7:37     ` Jeff Garzik
2005-05-27  7:47       ` Jens Axboe
2005-05-27  7:56         ` Jens Axboe [this message]
2005-05-27  8:24           ` Jeff Garzik
2005-05-27  8:27           ` Jeff Garzik
2005-05-27  8:28         ` Jeff Garzik
2005-05-27  8:35           ` Jens Axboe
2005-05-27  8:38             ` Jeff Garzik
2005-05-27  8:42               ` Jens Axboe
2005-05-27 23:47                 ` Jeff Garzik

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=20050527075621.GR1435@suse.de \
    --to=axboe@suse.de \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@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).