All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Anna Schumaker <bjschuma@netapp.com>
Cc: Trond.Myklebust@netapp.com, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 1/3] NFS: Use WRITE_PLUS for hole punches
Date: Tue, 29 Oct 2013 00:39:08 -0700	[thread overview]
Message-ID: <20131029073908.GC10889@infradead.org> (raw)
In-Reply-To: <1382972418-2249-2-git-send-email-bjschuma@netapp.com>

On Mon, Oct 28, 2013 at 11:00:16AM -0400, Anna Schumaker wrote:
> This patch implements a version of fallocate for NFS v4.  In the v4.2
> case, we use WRITE_PLUS with DATA_CONTENT_HOLE set to punch a hole in a
> file.  In NFS < v4.2, we fall back to the generic VFS fallocate
> implementation.

What generic VFS fallocate implementation do you fall back to?  Not only
can't I find a call to to it, nor does such a thing even exist.


  reply	other threads:[~2013-10-29  7:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-28 15:00 [PATCH 0/3] NFS: Add support for fallocate and llseek Anna Schumaker
2013-10-28 15:00 ` [PATCH 1/3] NFS: Use WRITE_PLUS for hole punches Anna Schumaker
2013-10-29  7:39   ` Christoph Hellwig [this message]
2013-10-29 12:41     ` Anna Schumaker
2013-11-05  9:37   ` Christoph Hellwig
2013-10-28 15:00 ` [PATCH 2/3] NFS: Allow for asynchronous WRITE_PLUS calls Anna Schumaker
2013-10-29  7:39   ` Christoph Hellwig
2013-10-29 12:44     ` Myklebust, Trond
2013-10-29 12:48       ` Hellwig Christoph
2013-10-29 13:05         ` Myklebust, Trond
2013-10-29 13:08           ` Hellwig Christoph
2013-10-29 13:21             ` Myklebust, Trond
2013-10-29 13:24               ` Hellwig Christoph
2013-10-29 13:41                 ` Myklebust, Trond
2013-10-29 13:44                 ` J. Bruce Fields
2013-10-28 15:00 ` [PATCH 3/3] NFS: Implement SEEK Anna Schumaker

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=20131029073908.GC10889@infradead.org \
    --to=hch@infradead.org \
    --cc=Trond.Myklebust@netapp.com \
    --cc=bjschuma@netapp.com \
    --cc=linux-nfs@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.