From: Benny Halevy <bhalevy@tonian.com>
To: lsf-pc@lists.linux-foundation.org
Cc: linux-fsdevel@vger.kernel.org,
NFS list <linux-nfs@vger.kernel.org>,
"J. Bruce Fields" <bfields@redhat.com>
Subject: [LSF/MM TOPIC] [ATTEND] linux-pnfs server implementations
Date: Sun, 25 Dec 2011 06:30:02 +0200 [thread overview]
Message-ID: <4EF6A6CA.1020606@tonian.com> (raw)
Now that the client side of pnfs is in the mainline kernel
I believe it is time to consider the inclusion of the server side.
I propose the following agenda for discussion
(order may change with no advance notice :)
* What's currently available in git://linux-nfs.org/~halevy/linux-pnfs.git
- What are the sub-projects
- How they relate to each other
* High-level design of the implementation
* Summary of generic changes in nfsd
* For each of the different sub-projects, briefly present:
- What does it do
- Benefits and Potential
- Limitations
- Status
- To-do
* Prerequisites for inclusion
* Discussion
Benny
next reply other threads:[~2011-12-25 4:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-25 4:30 Benny Halevy [this message]
2012-01-09 12:49 ` [LSF/MM TOPIC] [ATTEND] linux-pnfs server implementations Boaz Harrosh
2012-01-09 19:25 ` J. Bruce Fields
2012-01-11 7:44 ` Benny Halevy
2012-01-11 13:28 ` Boaz Harrosh
2012-01-11 14:11 ` J. Bruce Fields
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=4EF6A6CA.1020606@tonian.com \
--to=bhalevy@tonian.com \
--cc=bfields@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.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).