From: Chuck Lever <chuck.lever@oracle.com>
To: bfields@redhat.com
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH 0/3] NFSD support for FedFS junctions
Date: Mon, 29 Aug 2011 14:48:39 -0400 [thread overview]
Message-ID: <20110829184608.3305.93648.stgit@matisse.1015granger.net> (raw)
Hi Bruce-
Sometime soon we are going to have working and easy-to-install FedFS
user space components. These kernel patches are going to be needed
to make server-side FedFS support work.
Would you consider these for 3.2?
---
Trond Myklebust (3):
NFSD: Add a cache for fs_locations information
NFSD: Remove the ex_pathname field from struct svc_export
NFSD: Cleanup for nfsd4_path()
fs/nfsd/export.c | 15 +-----
fs/nfsd/nfs4xdr.c | 106 ++++++++++++++++++++++++++++++++-----------
fs/nfsd/nfsd.h | 7 +++
fs/nfsd/vfs.c | 15 ++++++
include/linux/nfsd/export.h | 2 -
5 files changed, 103 insertions(+), 42 deletions(-)
--
Chuck Lever
next reply other threads:[~2011-08-29 18:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-29 18:48 Chuck Lever [this message]
2011-08-29 18:48 ` [PATCH 1/3] NFSD: Cleanup for nfsd4_path() Chuck Lever
2011-08-29 18:49 ` [PATCH 2/3] NFSD: Remove the ex_pathname field from struct svc_export Chuck Lever
2011-08-29 18:55 ` [PATCH 0/3] NFSD support for FedFS junctions Chuck Lever
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=20110829184608.3305.93648.stgit@matisse.1015granger.net \
--to=chuck.lever@oracle.com \
--cc=bfields@redhat.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 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).