[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e74776f0-505b-8b4f-effd-519bce9bdc79@acm.org>
Date: Tue, 22 Mar 2022 19:57:27 -0700
From: Bart Van Assche <bvanassche@....org>
To: John Garry <john.garry@...wei.com>, axboe@...nel.dk,
damien.lemoal@...nsource.wdc.com, jejb@...ux.ibm.com,
martin.petersen@...cle.com, hch@....de, ming.lei@...hat.com,
hare@...e.de
Cc: 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 01/11] blk-mq: Add blk_mq_init_queue_ops()
On 3/22/22 03:39, John Garry wrote:
> Add an API to allocate a request queue which accepts a custom set of
> blk_mq_ops for that request queue.
>
> The reason which we may want custom ops is for queuing requests which we
> don't want to go through the normal queuing path.
Custom ops shouldn't be required for this. See e.g. how tmf_queue
is used in the UFS driver for an example of a queue implementation
with custom operations and that does not require changes of the block
layer core.
Thanks,
Bart.
Powered by blists - more mailing lists