Re: [PATCH v6 4/5] dax: for truncate/hole-punch, do zeroing through the driver if possible

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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?��.n��������+%������w��{.n�����{�����ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f




[Index of Archives]     [Reiser Filesystem Development]     [Ceph FS]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite National Park]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]     [Linux Media]

  Powered by Linux