[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8498ddc5-e5a5-16b3-bc70-2cfbc79d5258@huawei.com>
Date: Tue, 22 Mar 2022 11:36:03 +0000
From: John Garry <john.garry@...wei.com>
To: Christoph Hellwig <hch@....de>
CC: <axboe@...nel.dk>, <damien.lemoal@...nsource.wdc.com>,
<bvanassche@....org>, <jejb@...ux.ibm.com>,
<martin.petersen@...cle.com>, <ming.lei@...hat.com>,
<hare@...e.de>, <chenxiang66@...ilicon.com>,
<linux-block@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<linux-ide@...r.kernel.org>, <linux-scsi@...r.kernel.org>,
<dm-devel@...hat.com>, <beanhuo@...ron.com>
Subject: Re: [PATCH 03/11] libata: Send internal commands through the block
layer
On 22/03/2022 11:20, Christoph Hellwig wrote:
> On Tue, Mar 22, 2022 at 06:39:37PM +0800, John Garry wrote:
>> When SCSI HBA device drivers are required to process an ATA internal
>> command they still need a tag for the IO. This often requires the driver
>> to set aside a set of tags for these sorts of IOs and manage the tags
>> themselves.
>>
>> If we associate a SCSI command (and request) with an ATA internal command
>> then the tag is already provided, so introduce the change to send ATA
>> internal commands through the block layer with a set of custom blk-mq ops.
>>
>> note: I think that the timeout handling needs to be fixed up.
>
> Any reason to not just send them through an ATA_16 passthrough CDB and
> just use all the normal SCSI command handling?
>
> .
No reason that I know about.
TBH, I was hoping that someone woud have a better idea on how to do this
as what I was doing was messy.
Let me check it.
Cheers,
John
Powered by blists - more mailing lists