From: Jeff Garzik <jeff@garzik.org>
To: Grant Grundler <grundler@google.com>
Cc: 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 15:09:14 -0400 [thread overview]
Message-ID: <4A14555A.6080307@garzik.org> (raw)
In-Reply-To: <da824cf30905201010h1424e414idc3b01ecf7682005@mail.gmail.com>
Grant Grundler wrote:
> On Wed, May 20, 2009 at 12:00 AM, Jens Axboe <jens.axboe@oracle.com> wrote:
>> libata currently has a pretty dumb ATA_MAX_QUEUE loop for finding
>> a free tag to use. Instead of fixing that up, convert libata to
>> using block layer tagging - gets rid of code in libata, and is also
>> much faster.
> ...
>> @@ -1137,7 +1141,17 @@ static int ata_scsi_dev_config(struct scsi_device *sdev,
>>
>> depth = min(sdev->host->can_queue, ata_id_queue_depth(dev->id));
>> depth = min(ATA_MAX_QUEUE - 1, depth);
>> - scsi_adjust_queue_depth(sdev, MSG_SIMPLE_TAG, depth);
>> +
>> + /*
>> + * If this device is behind a port multiplier, we have
>> + * to share the tag map between all devices on that PMP.
>> + * Set up the shared tag map here and we get automatic.
>
> Automatic what?
>
>> + */
>> + if (dev->link->ap->pmp_link)
>> + scsi_init_shared_tag_map(sdev->host, ATA_MAX_QUEUE - 1);
>> +
>> + scsi_set_tag_type(sdev, MSG_SIMPLE_TAG);
>> + scsi_activate_tcq(sdev, depth);
>
> I just read Tejun's reply and it sounds right what he's saying.
> But can SATA controllers handle NCQ and !NCQ devices on the same port?
> Can the PMP handle it?
>
> If both can, I don't understand how a mixed config works today.
A mixed config over PMP works today by setting the proper depth iff NCQ
(== will not send too many cmds to device, if !NCQ) and using link-wide
tag allocation (== will not send too many cmds to link).
Jeff
next prev parent reply other threads:[~2009-05-20 19:09 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
2009-05-20 18:51 ` Jeff Garzik
2009-05-20 19:09 ` Jeff Garzik [this message]
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=4A14555A.6080307@garzik.org \
--to=jeff@garzik.org \
--cc=grundler@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.