[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1497491062.9288.19.camel@hpe.com>
Date: Thu, 15 Jun 2017 01:44:54 +0000
From: "Kani, Toshimitsu" <toshi.kani@....com>
To: "dan.j.williams@...el.com" <dan.j.williams@...el.com>,
"linux-nvdimm@...ts.01.org" <linux-nvdimm@...ts.01.org>
CC: "dm-devel@...hat.com" <dm-devel@...hat.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"viro@...iv.linux.org.uk" <viro@...iv.linux.org.uk>,
"hch@....de" <hch@....de>, "x86@...nel.org" <x86@...nel.org>,
"snitzer@...hat.com" <snitzer@...hat.com>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>
Subject: Re: [PATCH v3 05/14] dm: add ->flush() dax operation support
On Fri, 2017-06-09 at 13:24 -0700, Dan Williams wrote:
> Allow device-mapper to route flush operations to the
> per-target implementation. In order for the device stacking to work
> we need a dax_dev and a pgoff relative to that device. This gives
> each layer of the stack the information it needs to look up the
> operation pointer for the next level.
>
> This conceptually allows for an array of mixed device drivers with
> varying flush implementations.
>
> Cc: Toshi Kani <toshi.kani@....com>
> Reviewed-by: Mike Snitzer <snitzer@...hat.com>
> Signed-off-by: Dan Williams <dan.j.williams@...el.com>
Looks good to me.
Reviewed-by: Toshi Kani <toshi.kani@....com>
Thanks,
-Toshi
Powered by blists - more mailing lists