linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Mark Lord <liml@rtr.ca>
Cc: Gwendal Grignou <gwendal@google.com>,
	James Bottomley <James.Bottomley@hansenpartnership.com>,
	Grant Grundler <grundler@google.com>,
	Jens Axboe <jens.axboe@oracle.com>,
	linux-ide@vger.kernel.org, htejun@gmail.com
Subject: Re: [PATCH 1/2] libata: switch to using block layer tagging support
Date: Thu, 21 May 2009 13:27:41 -0400	[thread overview]
Message-ID: <4A158F0D.2090505@garzik.org> (raw)
In-Reply-To: <4A155AA5.3080704@rtr.ca>

Mark Lord wrote:
> Gwendal Grignou wrote:
>> Jeff, you're right, I made some mistakes:
>> - Reading SiI3132 doc again, it only supports 32 command per port, so
>> the tags must be share among all the drives behind the same port.
>> But other chipset does support up to 128 commands per port.
>> - Jens' patch is working when all disks support NCQ. Only when we have
>> a mix of drives with or without NCQ we have a problem.
> ..
> 
> Along those lines, the newer Marvell chipsets support up to 128 commands
> per host port.
> 
> I seem to recall that the Pacific Digital Qstor chip
> can manage an insane number of commands -- something like
> 32 per device per PM port [eg. (15 * 32) in total per host port].
> 
> Seems to be a widespread kind of thing for non-legacy chipsets.
> Someday we really ought to beef up libata to allow host-chipset queuing
> of non-NCQ commands, too.

SAS+SATA chips do not necessarily have per-port limits at all, even.

The limit may instead be a host-wide command queue size limit, rather 
than a per-port limit.

	Jeff





  reply	other threads:[~2009-05-21 17:27 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-20  6:59 [PATCH 0/2] libata: switch to block layer tagging Jens Axboe
2009-05-20  7:00 ` [PATCH 1/2] libata: switch to using block layer tagging support Jens Axboe
2009-05-20 11:53   ` Tejun Heo
2009-05-20 17:10   ` Grant Grundler
2009-05-20 18:08     ` Gwendal Grignou
2009-05-20 18:50       ` James Bottomley
2009-05-20 18:58         ` Jeff Garzik
2009-05-20 19:04           ` Jeff Garzik
2009-05-20 19:42             ` Gwendal Grignou
2009-05-20 19:47               ` Jeff Garzik
2009-05-21 13:44               ` Mark Lord
2009-05-21 17:27                 ` Jeff Garzik [this message]
2009-05-20 18:51       ` Jeff Garzik
2009-05-20 19:09     ` Jeff Garzik
2009-06-10 15:11   ` Jeff Garzik
2009-06-11  2:10     ` Tejun Heo
2009-05-20  7:01 ` [PATCH 2/2] block: add function for waiting for a specific free tag Jens Axboe
2009-05-20 11:55   ` Tejun Heo
2009-05-20 19:34     ` old-EH and SAS (was Re: [PATCH 2/2] block: add function for waiting for a specific free tag) Jeff Garzik
2009-05-21 16:34       ` Brian King
2009-05-20 17:28   ` [PATCH 2/2] block: add function for waiting for a specific free tag Grant Grundler
2009-05-20  7:53 ` [PATCH 0/2] libata: switch to block layer tagging Jeff Garzik
2009-05-20  7:57   ` Jens Axboe

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=4A158F0D.2090505@garzik.org \
    --to=jeff@garzik.org \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=grundler@google.com \
    --cc=gwendal@google.com \
    --cc=htejun@gmail.com \
    --cc=jens.axboe@oracle.com \
    --cc=liml@rtr.ca \
    --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 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).