[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAJfpegv6c6xR-ye9hj0AAiw_OsoYpHqTjH=jwAWPj4R2Wb6-1g@mail.gmail.com>
Date: Fri, 18 Jun 2021 09:12:49 +0200
From: Miklos Szeredi <miklos@...redi.hu>
To: "Richard W.M. Jones" <rjones@...hat.com>
Cc: linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
eblake@...hat.com, libguestfs@...hat.com,
Shachar Sharon <synarete@...il.com>
Subject: Re: [PATCH v4] fuse: Allow fallocate(FALLOC_FL_ZERO_RANGE)
On Tue, 15 Jun 2021 at 12:34, Richard W.M. Jones <rjones@...hat.com> wrote:
>
> On Tue, May 18, 2021 at 03:56:25PM +0200, Miklos Szeredi wrote:
> > On Wed, 12 May 2021 at 18:19, Richard W.M. Jones <rjones@...hat.com> wrote:
> > >
> > > The current fuse module filters out fallocate(FALLOC_FL_ZERO_RANGE)
> > > returning -EOPNOTSUPP. libnbd's nbdfuse would like to translate
> > > FALLOC_FL_ZERO_RANGE requests into the NBD command
> > > NBD_CMD_WRITE_ZEROES which allows NBD servers that support it to do
> > > zeroing efficiently.
> > >
> > > This commit treats this flag exactly like FALLOC_FL_PUNCH_HOLE.
> >
> > Thanks, applied.
>
> Hi Miklos, did this patch get forgotten?
It's in my internal patch queue. Will push to fuse.git#for-next in a few days.
Thanks,
Miklos
Powered by blists - more mailing lists