[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e771c366-2824-8774-4c90-9906992ee813@huawei.com>
Date: Fri, 12 Oct 2018 11:47:05 +0100
From: John Garry <john.garry@...wei.com>
To: "Martin K. Petersen" <martin.petersen@...cle.com>
CC: <jejb@...ux.vnet.ibm.com>, <linuxarm@...wei.com>,
<linux-scsi@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/7] hisi_sas: Misc bugfixes and an optimisation patch
On 11/10/2018 02:58, Martin K. Petersen wrote:
>
> John,
>
Hi Martin,
>> However it does block us in future from enabling SCSI MQ in the driver.
>
> We're going to remove the legacy I/O path so I'm not particularly keen
> on merging something that's going in the opposite direction.
What I really meant was that we cannot expose multiple queues to upper
layer, and nothing related to legacy IO path.
>
>> This is because the IPTT index must be a unique value per HBA. However,
>> if we switched to SCSI MQ, the block layer tag becomes unique per queue,
>> and not per HBA.
>
> That doesn't sound right.
>
Again, my wording my probably was not accurate. I meant that rq tag is
not unqiue across all hw queues.
As I mentioned in the thread that spawned from this, we actually can't
expose multiple hw queues at the moment. And, if we did, we find a
performance drop due to having to go back to manage this IPTT internally.
So how to handle? We're going to continue to work towards exposing
multiple queues to upper layer, but for the moment I think patch 6/7 is
a good change.
Please let me know.
Thanks,
John
Powered by blists - more mailing lists