linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalpak Shah <kalpak@clusterfs.com>
To: Andreas Dilger <adilger@clusterfs.com>
Cc: Theodore Tso <tytso@mit.edu>,
	Rupesh Thakare <rupesh@clusterfs.com>,
	linux-ext4@vger.kernel.org
Subject: Re: [RFC] store RAID stride in superblock
Date: Fri, 01 Jun 2007 02:32:29 +0530	[thread overview]
Message-ID: <1180645351.3922.1.camel@garfield> (raw)
In-Reply-To: <20070531201902.GF5181@schatzie.adilger.int>

On Thu, 2007-05-31 at 14:19 -0600, Andreas Dilger wrote:
> On May 31, 2007  12:21 -0400, Theodore Tso wrote:
> > On Thu, May 24, 2007 at 07:45:32PM +0530, Rupesh Thakare wrote:
> > > I've added "s_raid_stripe_width" parameter in superblock.
> > > I've also incorporated "s_raid_stride" and "s_raid_stripe_width" 
> > > parameters in tune2fs.
> > > The new options can be specified using  '-E options' in both mke2fs and 
> > > tune2fs.
> > > Both the Man pages (mke2fs and tune2fs) are updated accordingly.
> > > Patch is attached herewith.
> > 
> > Thanks.  I've used a different offset for the raid_stripe_width, to
> > avoid conflicting with Kalpak's mmp patch.  
> 
> Ah, we've been doing it the other way around here.  It makes sense to keep
> the s_raid_stripe_width fields together.  I think this code is preliminary
> enough that nobody has actually started using it yet.  Can you please post
> what the end of ext2_super_block looks like (whether you decide to reorder
> the fields or not).

I can update the MMP patches when I actually send them for inclusion. So
I think it makes sense to keep the s_raid_* fields together.

Thanks,
Kalpak.

> 
> Cheers, Andreas
> --
> Andreas Dilger
> Principal Software Engineer
> Cluster File Systems, Inc.
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2007-05-31 20:58 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-12  2:02 [RFC] store RAID stride in superblock Andreas Dilger
2007-05-12  2:21 ` Eric Sandeen
2007-05-12  8:11 ` Eric
2007-05-12  8:33   ` Alex Tomas
2007-05-12  9:32     ` Eric
2007-05-12  9:38       ` Alex Tomas
2007-05-12 16:14         ` Eric
2007-05-12 15:26   ` Andreas Dilger
2007-05-19  2:08 ` Theodore Tso
2007-05-24 11:44 ` Andreas Dilger
2007-05-24 14:15   ` Rupesh Thakare
2007-05-31 16:21     ` Theodore Tso
2007-05-31 20:19       ` Andreas Dilger
2007-05-31 21:02         ` Kalpak Shah [this message]
2007-05-31 21:33         ` Theodore Tso
2007-05-31 22:01           ` Eric Sandeen
2007-05-31 22:03           ` Andreas Dilger

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=1180645351.3922.1.camel@garfield \
    --to=kalpak@clusterfs.com \
    --cc=adilger@clusterfs.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=rupesh@clusterfs.com \
    --cc=tytso@mit.edu \
    /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).