public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: <Anna.Schumaker@netapp.com>
To: <bfields@fieldses.org>
Cc: <linux-nfs@vger.kernel.org>
Subject: [PATCH v3 0/3] NFSD: Add ALLOCATE and DEALLOCATE support
Date: Fri, 31 Oct 2014 16:53:43 -0400	[thread overview]
Message-ID: <1414788826-21474-1-git-send-email-Anna.Schumaker@Netapp.com> (raw)

From: Anna Schumaker <Anna.Schumaker@Netapp.com>

These patches add server support for the ALLOCATE and DEALLOCATE operations
part of NFS v4.2.

Changes in v3:
- Add back the do_fallocate() -> vfs_fallocate() patch
- Do Christoph's suggested cleanups to nfsd4_vfs_fallocate()

These patches and the corresponding client changes are available in the
[fallocate] branch of:

	git://git.linux-nfs.org/projects/anna/linux-nfs.git


Questions?  Comments?  Thoughts?

Anna


Anna Schumaker (3):
  VFS: Rename do_fallocate() to vfs_fallocate()
  nfsd: Add ALLOCATE support
  nfsd: Add DEALLOCATE support

 drivers/staging/android/ashmem.c |  2 +-
 fs/ioctl.c                       |  2 +-
 fs/nfsd/nfs4proc.c               | 51 ++++++++++++++++++++++++++++++++++++++++
 fs/nfsd/nfs4xdr.c                | 21 +++++++++++++++--
 fs/nfsd/vfs.c                    | 20 ++++++++++++++++
 fs/nfsd/vfs.h                    |  2 ++
 fs/nfsd/xdr4.h                   |  9 +++++++
 fs/open.c                        |  5 ++--
 include/linux/fs.h               |  2 +-
 mm/madvise.c                     |  2 +-
 10 files changed, 108 insertions(+), 8 deletions(-)

-- 
2.1.3


             reply	other threads:[~2014-10-31 20:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-31 20:53 Anna.Schumaker [this message]
2014-10-31 20:53 ` [PATCH v3 1/3] VFS: Rename do_fallocate() to vfs_fallocate() Anna.Schumaker
2014-10-31 20:53 ` [PATCH v3 2/3] nfsd: Add ALLOCATE support Anna.Schumaker
2014-11-06 20:08   ` J. Bruce Fields
2014-11-06 20:11     ` Anna Schumaker
2014-10-31 20:53 ` [PATCH v3 3/3] nfsd: Add DEALLOCATE support 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=1414788826-21474-1-git-send-email-Anna.Schumaker@Netapp.com \
    --to=anna.schumaker@netapp.com \
    --cc=bfields@fieldses.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox