From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: maillists0@gmail.com
Cc: "J. Bruce Fields" <bfields@fieldses.org>, linux-nfs@vger.kernel.org
Subject: Re: Proxy
Date: Mon, 03 May 2010 18:16:13 -0400 [thread overview]
Message-ID: <1272924973.7559.19.camel@localhost.localdomain> (raw)
In-Reply-To: <t2ndc64e7231005031414ob1ca0ebaze725bb73e712234d@mail.gmail.com>
On Mon, 2010-05-03 at 17:14 -0400, maillists0@gmail.com wrote:
> On Mon, May 3, 2010 at 3:25 PM, Trond Myklebust
> <trond.myklebust@fys.uio.no> wrote:
> > On Mon, 2010-05-03 at 14:56 -0400, J. Bruce Fields wrote:
> >> On Mon, May 03, 2010 at 12:53:15PM -0400, maillists0@gmail.com wrote:
> >> > With NFS4's support for referrals and Kerberos, it seems like the
> >> > original reasons to prevent re-exporting of an NFS share might no
> >> > longer exist. With fs-proxy making its way into the mainline kernel
> >> > and things like cachefilesd, there are also very good reasons to allow
> >> > it. A proxy server with a persistent cache could give the ability to
> >> > robustly use shares across a WAN or do failover pairs with no need for
> >> > more complex replication. Speaking as an end-user, this would be very
> >> > desirable.
> >> >
> >> > I see that others have implemented proxies with user-space NFS, which
> >> > seems reasonable but not optimal. What is the obstacle to allowing
> >> > re-exports with the standard nfs implentation? Is it possible at the
> >> > moment to patch a kernel to make this work? Anyone have experience
> >> > with it? Any input is appreciated.
> >>
> >> It's probably possible, but some kernel hacking would be required.
> >>
>
> Have a look at this old thing from 2006:
> http://www.usenix.org/event/fast07/tech/full_papers/gulati/gulati_html/nache.html
> . They claim to have implemented a proxy with only the tools I
> mentioned above, along with their own modified version of nfs to allow
> multi-hops.
>
> I have a workload of lots of reads/almost no writes, and their
> approach makes sense. It would be a great feature. Is something
> missing from that paper that makes it unrealistic?
Possibly not for your workload, but none of the issues Bruce and I
raised appear to be addressed in that paper.
Furthermore, we do know several of the authors, and none of them have
ever approached us with a proposal to merge their implementation. I
therefore assume that it was written more as a proof of concept in
support of the paper, rather than something IBM is actually planning to
market.
Cheers
Trond
next prev parent reply other threads:[~2010-05-03 22:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-03 16:53 Proxy maillists0
2010-05-03 18:56 ` Proxy J. Bruce Fields
2010-05-03 19:25 ` Proxy Trond Myklebust
2010-05-03 21:14 ` Proxy maillists0
2010-05-03 22:16 ` Trond Myklebust [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-21 9:10 Proxy Craig McDonald
[not found] <3F06C9859CA7D31194ED0000D1ECC4AB14C48B1B@pkcexv007.sprints pectrum.com>
2002-09-21 2:06 ` Proxy Ray Olszewski
2002-09-21 19:55 ` Proxy Bob Batson
2002-09-21 1:38 Proxy Le, Paul [Contractor]
2002-09-21 1:18 Proxy 'Alan Womack'
[not found] <3F06C9859CA7D31194ED0000D1ECC4AB14C48B12@pkcexv007.sprints pectrum.com>
2002-09-20 21:12 ` Proxy Ray Olszewski
2002-09-20 20:41 Proxy Le, Paul [Contractor]
2002-09-20 20:38 Proxy Alan Womack
2002-09-20 18:10 Proxy Craig McDonald
2002-09-20 17:32 Proxy Paul Kraus
2002-09-20 18:02 ` Proxy Ray Olszewski
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=1272924973.7559.19.camel@localhost.localdomain \
--to=trond.myklebust@fys.uio.no \
--cc=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=maillists0@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 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.