From: John Garry <john.garry@huawei.com>
To: Damien Le Moal <damien.lemoal@opensource.wdc.com>,
<linux-ide@vger.kernel.org>, <linux-scsi@vger.kernel.org>,
"Martin K . Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH v2 2/2] ata: libata-sata: Fix device queue depth control
Date: Tue, 27 Sep 2022 10:47:39 +0100 [thread overview]
Message-ID: <d2c4a043-e998-db98-1fe1-47b53516d7cc@huawei.com> (raw)
In-Reply-To: <60721293-14e2-98be-37af-ce7c1b227f44@opensource.wdc.com>
On 27/09/2022 10:28, Damien Le Moal wrote:
>> Sure, we can use sas_to_ata_dev() to get the ata_device.
>>
>> I am just suggesting my way such that we can have a consistent method to
>> get the ata_device between all libata users and we don't need to change
>> the ata_change_queue_depth() interface. It would be something like:
>>
>> struct ata_device *ata_scsi_find_dev(struct ata_port *ap, const struct
>> scsi_device *scsidev)
>> {
>> struct ata_link *link;
>> struct ata_device *dev;
>>
>> ata_for_each_link(link, ap, EDGE) {
>> ata_for_each_dev(dev, link, ENABLED) {
>> if (scsidev == dev->sdev)
>> return dev;
>> }
>> }
>> // todo: check pmp
>> return NULL;
>> }
> I see. Need to think about this one... This may also unify the pmp case.
> Are you OK with the patch as is though ?
I'm ok with your patchset, but let me test it and get back to you later
today.
We can improve with something
> like the above on top later. Really need to fix that qd setting as it is
> causing problems for testing devices with/without ncq commands.
Out of curiosity, are you considering your patchset for 6.0?
>
Thanks,
John
next prev parent reply other threads:[~2022-09-27 9:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-25 23:08 [PATCH v2 0/2] Fixes for ATA device queue depth control Damien Le Moal
2022-09-25 23:08 ` [PATCH v2 1/2] ata: libata-scsi: Fix initialization of device queue depth Damien Le Moal
2022-09-25 23:08 ` [PATCH v2 2/2] ata: libata-sata: Fix device queue depth control Damien Le Moal
2022-09-26 11:31 ` John Garry
2022-09-26 23:05 ` Damien Le Moal
2022-09-27 7:05 ` John Garry
2022-09-27 9:28 ` Damien Le Moal
2022-09-27 9:47 ` John Garry [this message]
2022-09-27 14:47 ` Damien Le Moal
2022-09-27 11:51 ` John Garry
2022-09-27 15:03 ` Damien Le Moal
2022-09-27 16:09 ` John Garry
2022-09-27 23:39 ` Damien Le Moal
2022-09-28 7:00 ` Damien Le Moal
2022-09-28 7:53 ` John Garry
2022-09-28 9:10 ` Damien Le Moal
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=d2c4a043-e998-db98-1fe1-47b53516d7cc@huawei.com \
--to=john.garry@huawei.com \
--cc=damien.lemoal@opensource.wdc.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
/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