All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Boaz Harrosh <bharrosh@panasas.com>
Cc: Benny Halevy <bhalevy@tonian.com>,
	lsf-pc@lists.linux-foundation.org, linux-fsdevel@vger.kernel.org,
	NFS list <linux-nfs@vger.kernel.org>,
	"J. Bruce Fields" <bfields@redhat.com>
Subject: Re: [LSF/MM TOPIC] [ATTEND] linux-pnfs server implementations
Date: Mon, 9 Jan 2012 14:25:17 -0500	[thread overview]
Message-ID: <20120109192517.GB16973@fieldses.org> (raw)
In-Reply-To: <4F0AE25C.5020706@panasas.com>

On Mon, Jan 09, 2012 at 02:49:32PM +0200, Boaz Harrosh wrote:
> On 12/25/2011 06:30 AM, Benny Halevy wrote:
> > 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.

We're also closing in on the basic 4.1 todo's, so I agree that it will
soon be time to talk about merging server-side pNFS.

> > 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

Understood that it may depend on where things stand in April, but: what
specifically do you think will be likely to require the attention of a
wider group of linux filesystem developers (ass opposed to just nfs
developers)?

--b.

> > * Discussion
> > 
> 
> Me too! This subject is close to my heart, as exofs is the most
> complete and advanced pNFSD base implementation. Last testing
> has demonstrated amazing performance and scalability. Saturating
> 10G from a single client and saturating 4*10G storage cluster
> from multiple clients.(Though there were problems with too many
> clients)

  reply	other threads:[~2012-01-09 19:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-25  4:30 [LSF/MM TOPIC] [ATTEND] linux-pnfs server implementations Benny Halevy
2011-12-25  4:30 ` Benny Halevy
2012-01-09 12:49 ` Boaz Harrosh
2012-01-09 19:25   ` J. Bruce Fields [this message]
2012-01-11  7:44     ` Benny Halevy
2012-01-11  7:44       ` Benny Halevy
2012-01-11 13:28       ` Boaz Harrosh
2012-01-11 14:11         ` J. Bruce Fields
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=20120109192517.GB16973@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=bfields@redhat.com \
    --cc=bhalevy@tonian.com \
    --cc=bharrosh@panasas.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 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.