[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1462909729.29294.21.camel@intel.com>
Date: Tue, 10 May 2016 19:49:01 +0000
From: "Verma, Vishal L" <vishal.l.verma@...el.com>
To: "hch@...radead.org" <hch@...radead.org>,
"axboe@...com" <axboe@...com>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-block@...r.kernel.org" <linux-block@...r.kernel.org>,
"xfs@....sgi.com" <xfs@....sgi.com>,
"linux-nvdimm@...1.01.org" <linux-nvdimm@...1.01.org>,
"jmoyer@...hat.com" <jmoyer@...hat.com>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"Williams, Dan J" <dan.j.williams@...el.com>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
"ross.zwisler@...ux.intel.com" <ross.zwisler@...ux.intel.com>,
"linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>,
"boaz@...xistor.com" <boaz@...xistor.com>,
"david@...morbit.com" <david@...morbit.com>,
"jack@...e.cz" <jack@...e.cz>
Subject: Re: [PATCH v6 4/5] dax: for truncate/hole-punch, do zeroing through
the driver if possible
On Tue, 2016-05-10 at 12:25 -0700, Christoph Hellwig wrote:
> Hi Vishal,
>
> can you also pick up the my patch to add a low-level __dax_zero_range
> that I cced you on? That way we can avoid a nasty merge conflict with
> my xfs/iomap changes.
Good idea - I'll do that for the next posting. I'll wait a day or two
for any additional reviews/acks.
I'm looking to get all this into a branch in the nvdimm tree once Jan
splits up his dax-locking series..
Mostly I guess I'm looking for a yay or nay for the block layer changes
(patch 2). Jens?
Powered by blists - more mailing lists