[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <yq14k0dldlx.fsf@ca-mkp.ca.oracle.com>
Date: Tue, 21 Jun 2022 20:57:42 -0400
From: "Martin K. Petersen" <martin.petersen@...cle.com>
To: John Garry <john.garry@...wei.com>
Cc: <axboe@...nel.dk>, <damien.lemoal@...nsource.wdc.com>,
<bvanassche@....org>, <hch@....de>, <jejb@...ux.ibm.com>,
<martin.petersen@...cle.com>, <hare@...e.de>, <satishkh@...co.com>,
<sebaddel@...co.com>, <kartilak@...co.com>,
<linux-doc@...r.kernel.org>, <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 v2 0/6] blk-mq: Add a flag for reserved requests series
John,
> In [0] I included "blk-mq: Add a flag for reserved requests" to
> identify if a request is 'reserved' for special handling. Doing this
> is easier than passing a 'reserved' arg to the blk_mq_ops
> callbacks. Indeed, only 1x timeout implementation or blk-mq iter
> function actually uses the 'reserved' arg (or 3x if you count SCSI
> core and FNIC SCSI driver). So this series drops the 'reserved' arg
> for these timeout and iter functions. Christoph suggested that I try
> to upstream now.
Reviewed-by: Martin K. Petersen <martin.petersen@...cle.com>
--
Martin K. Petersen Oracle Linux Engineering
Powered by blists - more mailing lists