From: John Garry <john.garry@huawei.com>
To: Damien Le Moal <damien.lemoal@opensource.wdc.com>,
<jejb@linux.ibm.com>, <martin.petersen@oracle.com>,
<bvanassche@acm.org>, <ming.lei@redhat.com>, <hch@lst.de>,
<hare@suse.de>
Cc: <linux-ide@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-scsi@vger.kernel.org>, <martin.wilck@suse.com>
Subject: Re: [PATCH 0/2] scsi/libata: A potential tagging fix and improvement
Date: Wed, 16 Mar 2022 08:15:41 +0000 [thread overview]
Message-ID: <1bde0883-bfbb-ea54-82f0-4e53b884b24b@huawei.com> (raw)
In-Reply-To: <b77e681d-d180-7434-1675-1fcb10ef4abf@opensource.wdc.com>
On 16/03/2022 03:25, Damien Le Moal wrote:s
Hi Damien,
> I tested this and it is working fine for me. This actually solves the QD
> not changing problem I had detected with the pm80xx driver.
> Now, doing this:
>
> # cat /sys/block/sde/device/queue_depth
> 32
> # echo 16 > /sys/block/sde/device/queue_depth
> # cat /sys/block/sde/device/queue_depth
> 16
>
Having this working is down to the first patch. So I will resend that
patch today separately so that we may look to have it included in 5.18,
even though we're so late in the cycle...
> is working as expected.
>
> See my comments on patch 2 for getting final ack and tested tags:)
OK, Thanks,
John
prev parent reply other threads:[~2022-03-16 8:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 10:39 [PATCH 0/2] scsi/libata: A potential tagging fix and improvement John Garry
2022-03-15 10:39 ` [PATCH 1/2] scsi: core: Fix sbitmap depth in scsi_realloc_sdev_budget_map() John Garry
2022-03-15 14:33 ` Bart Van Assche
2022-03-15 15:11 ` John Garry
2022-03-15 14:38 ` Ming Lei
2022-03-15 10:39 ` [PATCH RFC 2/2] libata: Use scsi cmnd budget token for qc tag for SAS host John Garry
2022-03-16 3:21 ` Damien Le Moal
2022-03-16 8:23 ` John Garry
2022-03-16 8:34 ` Christoph Hellwig
2022-03-16 10:46 ` John Garry
2022-03-16 23:23 ` Damien Le Moal
2022-03-16 3:25 ` [PATCH 0/2] scsi/libata: A potential tagging fix and improvement Damien Le Moal
2022-03-16 8:15 ` John Garry [this message]
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=1bde0883-bfbb-ea54-82f0-4e53b884b24b@huawei.com \
--to=john.garry@huawei.com \
--cc=bvanassche@acm.org \
--cc=damien.lemoal@opensource.wdc.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=jejb@linux.ibm.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=martin.wilck@suse.com \
--cc=ming.lei@redhat.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