linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@clusterfs.com>
To: linux-ext4@vger.kernel.org
Cc: Theodore Ts'o <tytso@mit.edu>
Subject: Re: [RFC] store RAID stride in superblock
Date: Thu, 24 May 2007 05:44:42 -0600	[thread overview]
Message-ID: <20070524114442.GA12526@schatzie.adilger.int> (raw)
In-Reply-To: <20070512020248.GQ6375@schatzie.adilger.int>

On May 22, 2007  01:22 +0530, Kalpak Shah wrote:
>         __u16   s_raid_stride;          /* RAID stride */
> -       __u16   s_pad;                  /* Padding */
> +       __u16   s_mmp_interval;         /* Wait for # seconds in MMP
> checking */
> +       __u64   s_mmp_block;            /* Block for multi-mount protection
> */

Ted, I just noticed this updated patch w.r.t. your recent s_raid_stride
addition.  I also want to have a separate parameter for "s_raid_stripe_width"
which is normally N * s_raid_stride, where N is the number of disks in a
RAID 5 N+1 (or RAID 6 N+2) parity stripe.  This is for delalloc+mballoc to
allow it to align and size new allocations so that writes do not impose
read-modify-write overhead on the RAID stripes.

My understanding from the code is that s_raid_stride is to put the bitmaps
for different groups on different disks to avoid always having a single
disk busy with bitmap updates.


Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.

  parent reply	other threads:[~2007-05-24 11:44 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 [this message]
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
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=20070524114442.GA12526@schatzie.adilger.int \
    --to=adilger@clusterfs.com \
    --cc=linux-ext4@vger.kernel.org \
    --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).