linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Richard W.M. Jones" <rjones@redhat.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	eblake@redhat.com, libguestfs@redhat.com,
	Shachar Sharon <synarete@gmail.com>
Subject: Re: [PATCH v4] fuse: Allow fallocate(FALLOC_FL_ZERO_RANGE)
Date: Tue, 15 Jun 2021 11:33:57 +0100	[thread overview]
Message-ID: <20210615103357.GP26415@redhat.com> (raw)
In-Reply-To: <CAJfpegv=C-tUwbAi+JMWrNb+pai=HiAU8YCDunE5yUZB7qMK1g@mail.gmail.com>

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@redhat.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?

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-top is 'top' for virtual machines.  Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
http://people.redhat.com/~rjones/virt-top


  reply	other threads:[~2021-06-15 10:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-12 16:18 [PATCH v4] fuse: Allow fallocate(FALLOC_FL_ZERO_RANGE) Richard W.M. Jones
2021-05-12 16:18 ` Richard W.M. Jones
2021-05-18 13:56   ` Miklos Szeredi
2021-06-15 10:33     ` Richard W.M. Jones [this message]
2021-06-18  7:12       ` Miklos Szeredi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210615103357.GP26415@redhat.com \
    --to=rjones@redhat.com \
    --cc=eblake@redhat.com \
    --cc=libguestfs@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=synarete@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).