[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJfpegv=C-tUwbAi+JMWrNb+pai=HiAU8YCDunE5yUZB7qMK1g@mail.gmail.com>
Date: Tue, 18 May 2021 15:56:25 +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 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.
Miklos
Powered by blists - more mailing lists