[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1515455227.2909.45.camel@wdc.com>
Date: Mon, 8 Jan 2018 23:47:09 +0000
From: Bart Van Assche <Bart.VanAssche@....com>
To: "jbacik@...com" <jbacik@...com>, "tj@...nel.org" <tj@...nel.org>,
"jack@...e.cz" <jack@...e.cz>, "clm@...com" <clm@...com>,
"axboe@...nel.dk" <axboe@...nel.dk>
CC: "kernel-team@...com" <kernel-team@...com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"peterz@...radead.org" <peterz@...radead.org>,
"linux-btrfs@...r.kernel.org" <linux-btrfs@...r.kernel.org>,
"linux-block@...r.kernel.org" <linux-block@...r.kernel.org>,
"jianchao.w.wang@...cle.com" <jianchao.w.wang@...cle.com>
Subject: Re: [PATCH 7/8] blk-mq: remove REQ_ATOM_STARTED
On Mon, 2018-01-08 at 11:15 -0800, Tejun Heo wrote:
> After the recent updates to use generation number and state based
> synchronization, we can easily replace REQ_ATOM_STARTED usages by
> adding an extra state to distinguish completed but not yet freed
> state.
>
> Add MQ_RQ_COMPLETE and replace REQ_ATOM_STARTED usages with
> blk_mq_rq_state() tests. REQ_ATOM_STARTED no longer has any users
> left and is removed.
Reviewed-by: Bart Van Assche <bart.vanassche@....com>
Powered by blists - more mailing lists