[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220322111848.GA29270@lst.de>
Date: Tue, 22 Mar 2022 12:18:48 +0100
From: Christoph Hellwig <hch@....de>
To: John Garry <john.garry@...wei.com>
Cc: axboe@...nel.dk, damien.lemoal@...nsource.wdc.com,
bvanassche@....org, jejb@...ux.ibm.com, martin.petersen@...cle.com,
hch@....de, 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 01/11] blk-mq: Add blk_mq_init_queue_ops()
On Tue, Mar 22, 2022 at 06:39:35PM +0800, 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.
Eww. I really do not think we should do separate ops per queue, as that
is going to get us into a deep mess eventually.
Powered by blists - more mailing lists