From: Benny Halevy <bhalevy@panasas.com>
To: "Smets, Jan (Jan)" <jan.smets@alcatel-lucent.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: NFSv4.1 status
Date: Fri, 18 Jun 2010 10:58:13 -0400 [thread overview]
Message-ID: <4C1B8985.8090808@panasas.com> (raw)
In-Reply-To: <14C7F4F06DB5814AB0DE29716C4F6D670B6534E7@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com>
On Jun. 16, 2010, 21:05 -0400, "Smets, Jan (Jan)" <jan.smets@alcatel-lucent.com> wrote:
> Hi list
>
> I would like to know what status the NFS 4.1 (pNFS) development is in.
Hi Jan,
Our main focus in development right now is submitting basic implementation for the pnfs files layout
and continuing to improve also the object and block layout implementations that will follow.
>
> Can it be tested? If yes, is there any guide what exactly I can do with it at this stage (and how) ?
The guides are placed on our wiki:
http://wiki.linux-nfs.org/wiki/index.php/PNFS_prototype_design
> I already have the pnfs capable kernel, but it's unclear to me what userland tools I need (server side).
What are you testing on the back end?
>
> At the end I would like multiple dataservers that stripe data,
That should not be a problem.
> and multiple metadata servers that also stripe data and all with failover/redundancy/load balancing stuff. But maybe I'm whishing for too much, yet.
Yes, you're aiming too high at this point.
That said, contributing code to do all that will be truly appreciated! ;-)
Benny
>
> Thanks
>
> - Jan
>
>
>
>
>
>
>
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2010-06-18 14:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-17 1:05 NFSv4.1 status Smets, Jan (Jan)
2010-06-18 14:58 ` Benny Halevy [this message]
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=4C1B8985.8090808@panasas.com \
--to=bhalevy@panasas.com \
--cc=jan.smets@alcatel-lucent.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).