From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: Marc Eshel <eshel@almaden.ibm.com>
Cc: Peng Tao <bergwolf@gmail.com>,
bhalevy@tonian.com, Boaz Harrosh <bharrosh@panasas.com>,
Garth Gibson <garth@panasas.com>,
Fred Isaman <iisaman@netapp.com>,
linux-nfs@vger.kernel.org, Matt Benjamin <matt@linuxbox.com>
Subject: Re: [PATCH 0/4] nfs41: allow layoutget at pnfs_do_multiple_writes
Date: Tue, 29 Nov 2011 19:37:05 -0500 [thread overview]
Message-ID: <1322613425.11286.86.camel@lade.trondhjem.org> (raw)
In-Reply-To: <OF5755ED9D.CC1FAA6E-ON88257958.00014359-88257958.0001D4D0@us.ibm.com>
On Tue, 2011-11-29 at 16:20 -0800, Marc Eshel wrote:
> You ignored my main point, I was talking about the server side, my point
> was that there is nothing to build on on the serve side since the pNFS
> Linux server is not happening.
> Marc.
Sorry. I misunderstood your concern. As far as I know, the main problem
there is also one of investment: nobody has stepped up to help Bruce
write a pNFS server.
I'm less worried about this now than I was earlier, because other open
source efforts are gaining traction (see Ganesha - which is being
sponsored by IBM, and projects such as Tigran's java based pNFS server).
The other point is that we've developed client test-rigs that don't
depend on the availability of a Linux server (newpynfs and the pynfs
based proxy).
Cheers
Trond
> From:
> Trond Myklebust <Trond.Myklebust@netapp.com>
> To:
> Marc Eshel <eshel@almaden.ibm.com>
> Cc:
> Peng Tao <bergwolf@gmail.com>, bhalevy@tonian.com, Boaz Harrosh
> <bharrosh@panasas.com>, Garth Gibson <garth@panasas.com>, Fred Isaman
> <iisaman@netapp.com>, linux-nfs@vger.kernel.org, Matt Benjamin
> <matt@linuxbox.com>
> Date:
> 11/29/2011 04:08 PM
> Subject:
> Re: [PATCH 0/4] nfs41: allow layoutget at pnfs_do_multiple_writes
>
>
>
> On Tue, 2011-11-29 at 15:49 -0800, Marc Eshel wrote:
> > The only 1 cent that I can add to this argument is that I was led to
> > believe by you and others that Linux kernel don't add functionality on
> the
> > client side that is not supported on the server side. Last time I made
> > this point I was told that it is ok if they are of by a version or two.
> > You made it clear that this is no longer true and that the Linux client
> > and server are now independent of each other. I spent time working on
> the
> > server side believing that the client and server will progress more or
> > less together, disappointed to find out that it is not the case any
> more.
> > Marc.
>
> I don't know how to manage layout segments in a way that meets the pNFS
> goals of scalability and performance, and neither you nor the pNFS spec
> have told me how to do this.
>
> If IBM wants a client that implements layout segments, then it is _your_
> responsibility to:
> A. Convince me that it is an implementable part of the spec.
> B. Provide me with an implementation that deals all with the
> concerns that I have.
>
> IOW: nobody has ever promised IBM that the community would do all your
> client work for you. EMC, NetApp and Panasas have implemented (most of)
> the bits that they cared about; any bits that they haven't implemented
> and that you care about are up to you.
>
--
Trond Myklebust
Linux NFS client maintainer
NetApp
Trond.Myklebust@netapp.com
www.netapp.com
next prev parent reply other threads:[~2011-11-30 0:37 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-03 4:52 [PATCH 0/4] nfs41: allow layoutget at pnfs_do_multiple_writes Peng Tao
2011-11-29 21:34 ` Boaz Harrosh
2011-11-29 21:50 ` Boaz Harrosh
2011-11-29 21:57 ` Trond Myklebust
2011-11-29 22:40 ` Boaz Harrosh
2011-11-29 22:47 ` Trond Myklebust
2011-11-29 22:58 ` Boaz Harrosh
2011-11-29 23:30 ` Trond Myklebust
2011-11-29 23:49 ` Marc Eshel
2011-11-30 0:08 ` Trond Myklebust
2011-11-30 0:20 ` Marc Eshel
2011-11-30 0:37 ` Trond Myklebust [this message]
2011-11-30 0:50 ` Boaz Harrosh
2011-11-30 19:39 ` J. Bruce Fields
2011-11-30 0:52 ` Marc Eshel
2011-11-30 19:44 ` J. Bruce Fields
2011-12-01 9:47 ` Benny Halevy
2011-12-01 11:14 ` J. Bruce Fields
2011-12-01 11:48 ` J. Bruce Fields
2011-11-30 0:42 ` Boaz Harrosh
2011-11-30 0:24 ` Boaz Harrosh
2011-11-30 0:58 ` Trond Myklebust
2011-11-30 1:46 ` Boaz Harrosh
2011-11-30 2:07 ` Trond Myklebust
2011-11-30 3:08 ` Boaz Harrosh
2011-11-30 12:33 ` Benny Halevy
2011-11-30 0:37 ` Matt W. Benjamin
2011-11-30 0:48 ` Matt W. Benjamin
2011-11-30 1:01 ` Trond Myklebust
2011-11-30 1:03 ` Matt W. Benjamin
2011-11-29 23:01 ` Trond Myklebust
2011-11-29 23:47 ` Boaz Harrosh
2011-11-30 3:16 ` tao.peng
2011-11-30 3:50 ` Boaz Harrosh
2011-11-30 5:05 ` tao.peng
2011-11-30 12:42 ` Benny Halevy
2011-12-03 4:52 ` [PATCH 1/4] nfsv41: export pnfs_find_alloc_layout Peng Tao
2011-12-03 4:52 ` [PATCH 2/4] nfsv41: add and export pnfs_find_get_layout_locked Peng Tao
2011-12-03 4:52 ` [PATCH 3/4] nfsv41: get lseg before issue LD IO if pgio doesn't carry lseg Peng Tao
2011-11-30 13:01 ` Benny Halevy
2011-11-30 13:20 ` Peng Tao
2011-12-03 4:52 ` [PATCH 4/4] pnfsblock: do ask for layout in pg_init Peng Tao
2011-11-29 16:40 ` Trond Myklebust
2011-11-29 17:25 ` Peng Tao
2011-11-29 17:43 ` Trond Myklebust
2011-11-30 2:55 ` tao.peng
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=1322613425.11286.86.camel@lade.trondhjem.org \
--to=trond.myklebust@netapp.com \
--cc=bergwolf@gmail.com \
--cc=bhalevy@tonian.com \
--cc=bharrosh@panasas.com \
--cc=eshel@almaden.ibm.com \
--cc=garth@panasas.com \
--cc=iisaman@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=matt@linuxbox.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).