linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benny Halevy <bhalevy@panasas.com>
To: sfaibish <sfaibish@emc.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: Resent: [pnfs][PATCH 0/3] pnfs-blocklayout client: adding support for complex volume structure
Date: Thu, 10 Jun 2010 18:44:09 +0300	[thread overview]
Message-ID: <4C110849.8000500@panasas.com> (raw)
In-Reply-To: <op.vdsfeiz2unckof-sXut7+96orlxdPWQvOaHCoI83tS8F2Zb0E9HWUfgJXw@public.gmane.org>

On Jun. 04, 2010, 21:09 +0300, sfaibish <sfaibish@emc.com> wrote:
> Apply against 2.6.34-rc3 pnfs branch. For pNFS client submission. Only  
> touches
> the block layout driver.

Sorin, I suggest you guys test this set with the linux-pnfs 2.6.35-rc2 tree
against both the EMC and the spnfs-block server in the Ann Arbor Bakeathon
and resend.

I admit I didn't review this thoroughly yet and hopefully we can find some
time to do it together in Ann Arbor.

Benny

> 
> This patch set implements support for the complex volumes structures such  
> as
> stripe of multiple volumes in a single metavolume and slice of metavolumes  
> into
> smaller metavolumes. The patch set is specific to pnfs blocklayout and uses
> simple rpc pipefs to generate messages that are passed to the userland  
> which is
> using an daemon to discover all the devices in the message. The userspace  
> daemon
> patches will be sent in a separate patch set.
> 
> The patch set replaces the current single volume implementation of the  
> pnfs blocklayout
> that has performance limitations and cannot support wide striped file  
> systems.
> The wide stripe is imperious to the performance scalability both for  
> single and multiple
> clients configurations. These patches address only the pnfs blocklayout  
> client. Similar
> patches will be implemented for the pnfsd block layout served in the  
> second phase.
> 
> 0001-pnfs-block-layout-add-simple-rpc-pipefs.patch
> 0002-pnfs-block-layout-remove-device-creation-or-remove-from-kernel.patch
> 0003-pnfs-block-layout-add-block-device-pipe-processing-based-on-simple-rpc.patch
> 
> Testing:
> CONFIG_NFS_V4_1 set:
> 
> NFSv4.1/pNFS mounts:
> Connectathon tests pass against Celerra/pNFS block layout server with both  
> simple
> volumes and complex volumes stripe on 4 volumes and using a slice of half  
> of the
> striped metavolume.
> 
> CONFIG_NFS_V4_1 not set:
> NFSv4.0 mount passes Connectathon tests.
> 
> /Sorin
> 
> --
> 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
> 

  parent reply	other threads:[~2010-06-10 15:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-04 18:09 Resent: [pnfs][PATCH 0/3] pnfs-blocklayout client: adding support for complex volume structure sfaibish
     [not found] ` <op.vdsfeiz2unckof-sXut7+96orlxdPWQvOaHCoI83tS8F2Zb0E9HWUfgJXw@public.gmane.org>
2010-06-04 18:15   ` [pnfs][PATCH 2/3] pnfs-blocklayout client: remove device creation or remove from kernel sfaibish
     [not found]     ` <op.vdsfn9iounckof-sXut7+96orlxdPWQvOaHCoI83tS8F2Zb0E9HWUfgJXw@public.gmane.org>
2010-06-04 18:19       ` [pnfs][PATCH 3/3] pnfs-blocklayout client: add block device pipe processing based on simple rpc pipefs sfaibish
     [not found]         ` <op.vdsfuksdunckof-sXut7+96orlxdPWQvOaHCoI83tS8F2Zb0E9HWUfgJXw@public.gmane.org>
2010-06-04 18:25           ` [pnfs] [PATCH " Christoph Hellwig
2010-06-04 18:31             ` sfaibish
2010-06-09  0:12             ` J. Bruce Fields
2010-06-10 15:44   ` Benny Halevy [this message]
2010-06-10 17:07     ` Resent: [pnfs][PATCH 0/3] pnfs-blocklayout client: adding support for complex volume structure sfaibish
     [not found]       ` <op.vd3gi4n5unckof-sXut7+96orlxdPWQvOaHCoI83tS8F2Zb0E9HWUfgJXw@public.gmane.org>
2010-06-10 17:10         ` Benny Halevy
2010-06-10 17:19           ` sfaibish

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=4C110849.8000500@panasas.com \
    --to=bhalevy@panasas.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=sfaibish@emc.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).