From: Jeff Garzik <jeff@garzik.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Gwendal Grignou <gwendal@google.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: Wed, 20 May 2009 14:58:49 -0400 [thread overview]
Message-ID: <4A1452E9.7000204@garzik.org> (raw)
In-Reply-To: <1242845440.2881.74.camel@localhost.localdomain>
James Bottomley wrote:
> On Wed, 2009-05-20 at 11:08 -0700, Gwendal Grignou wrote:
>> Form the ATA and SATA spec, NCQ is per device. It is possible to
>> assign the same tag on different port, the disks and PMP will not
>> care.
>> However, today, we assign tag on a port basis [see
>> __ata_qc_from_tag()], therefore only 32 commands can be inflight to
>> all devices behind a given port.
>>
>> Being able to a do a mapping qc <---> {pmp port, tag} instead of just
>> qc <---> {tag} will provide a performance boost when disks supporting
>> NCQ are connected behind a PMP. Maybe it can be done, by moving qcmd
>> from ata_port to ata_link.
>>
>> As Tejun said, the patch needs more work to be able to support same
>> tag used on 2 different links behind the same port.
>> Also, given we are changing the amount of commands we sent to the
>> controller, we would have to change can_queue from ATA_MAX_QUEUE to
>> ATA_MAX_QUEUE*n, where n is the number of ports supported by the
>> controller [max SATA_PMP_MAX_PORTS, but some controller, like SiI3132
>> only supports 5 devices, and other may only support n = 1]
>>
>> When done, the patch will require a great amount of testing, given we
>> will exercise the controllers in a brand new way. A white list might
>> be necessary.
>>
>> Jens, using SCSI tagging for ata commands is a great idea, but it is
>> no small feat...
>
> So realistically, you want one block queue per PMP port rather than an
> artificial limits adjustment on the single queue per output phy ... this
> shouldn't be too hard: it is exactly the way the SAS transport class
> (and libsas) works today for expander connected SAS devices.
Well... The limiting factor is "ATA command slots per SATA phy", which
defines $N active ATA commands per port. If a SATA NCQ device is
attached, you may have $N active ATA commands queued. If two SATA NCQ
devices are attached to a PMP, which is attached to the SATA controller,
the two devices share the limit of $N active ATA commands queued. If 32
devices are attached to a PMP, all 32 devices share the $N command queue
limit.
But additionally, as Tejun demonstrated, you might have a mix of NCQ and
non-NCQ devices attached to the PMP.
Thus, it is a case of nested limits:
- $N maximum active commands per port; typically N==32
- $M maximum active commands per device; typically N==1 or N==32
Regards,
Jeff
next prev parent reply other threads:[~2009-05-20 18:58 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 [this message]
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
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=4A1452E9.7000204@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=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).