From: Eric Sandeen <sandeen@redhat.com>
To: Andreas Dilger <adilger@clusterfs.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [RFC] store RAID stride in superblock
Date: Fri, 11 May 2007 21:21:24 -0500 [thread overview]
Message-ID: <464524A4.9060209@redhat.com> (raw)
In-Reply-To: <20070512020248.GQ6375@schatzie.adilger.int>
Andreas Dilger wrote:
> It is possible to specify the RAID stride to mke2fs allow it to optimize
> the layout of the bitmaps. With the new mballoc it is also possible to
> tell it via a mount option to do large allocations aligned on the RAID
> stride (by default it aligns on 1MB boundaries from the start of the LUN).
>
> What would be rather convenient is to store the RAID stride value in the
> superblock. That would spare a lot of hassle on the part of the admin
> to tune the filesystem optimally for the underlying storage. There is
> also a library used in the XFS tools that knows how to probe various
> kinds of block devices (e.g. MD RAID, LVM/DM, etc) to get their storage
> layout that would avoid the need for the user to specify anything.
>
> Any thoughts on this?
I think it sounds great. I think ext4 would benefit greatly from
knowing a bit more about the underlying device geometry & allocating
accordingly...
-Eric
next prev parent reply other threads:[~2007-05-12 2:21 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 [this message]
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
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=464524A4.9060209@redhat.com \
--to=sandeen@redhat.com \
--cc=adilger@clusterfs.com \
--cc=linux-ext4@vger.kernel.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).