[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6d84b3cb-a362-05ae-c7c3-62d3eddf9f02@acm.org>
Date: Fri, 17 Jun 2022 09:29:28 -0700
From: Bart Van Assche <bvanassche@....org>
To: John Garry <john.garry@...wei.com>, axboe@...nel.dk,
damien.lemoal@...nsource.wdc.com, hch@....de, jejb@...ux.ibm.com,
martin.petersen@...cle.com, hare@...e.de, satishkh@...co.com,
sebaddel@...co.com, kartilak@...co.com
Cc: linux-rdma@...r.kernel.org, linux-mmc@...r.kernel.org,
linux-nvme@...ts.infradead.org, linux-s390@...r.kernel.org,
linux-scsi@...r.kernel.org, mpi3mr-linuxdrv.pdl@...adcom.com,
linux-block@...r.kernel.org, linux-kernel@...r.kernel.org,
nbd@...er.debian.org
Subject: Re: [PATCH 3/5] blk-mq: Drop blk_mq_ops.timeout 'reserved' arg
On 6/17/22 03:55, John Garry wrote:
> With new API blk_mq_is_reserved_rq() we can tell if a request is from
> the reserved pool, so stop passing 'reserved' arg. There is actually
> only a single user of that arg for all the callback implementations, which
> can use blk_mq_is_reserved_rq() instead.
>
> This will also allow us to stop passing the same 'reserved' around the
> blk-mq iter functions next.
Reviewed-by: Bart Van Assche <bvanassche@....org>
Powered by blists - more mailing lists