From: Eric <erpo41@gmail.com>
To: linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Re: [RFC] store RAID stride in superblock
Date: Sat, 12 May 2007 09:14:17 -0700 [thread overview]
Message-ID: <1178986457.6021.22.camel@eric-laptop> (raw)
In-Reply-To: <46458AF9.404@clusterfs.com>
[-- Attachment #1: Type: text/plain, Size: 1447 bytes --]
> > Perhaps the filesystem driver or mkfs could
> > probe for the stride in those cases? If the code asks for, say, 10MiB of
> > data from the block device and it gets back sectors that are spaced
> > 128KiB apart before it gets the rest of the data, it can make an
> > intelligent guess about the stride.
>
> do you mean incorporation
> storage benchmark in the mount procedure?
Yes. If the benefits of automatically aligning on-disk data structures
to the stride of the array are great enough, then a storage
mini-benchmark may be of use.
For example, suppose we have an array with a stride of 1MiB and the
filesystem driver requests 10MiB of contiguous data from the start of
the block device. Then the data at +0MiB from the start of the device,
the data at +1MiB, the data at +2MiB, and so on ought to arrive earlier
the data at, say, +0.5MiB, +1.5MiB and +2.5MiB. This would allow the
filesystem driver to detect the stride even when the striping isn't
being done by the MD or LVM/DM drivers in Linux (which, apparently, have
well-defined interfaces for discovering the stride in software).
I imagine this would work well for a run-of-the-mill hardware RAID card
in a PC. However, as you pointed out in your original email, there are
SANs to be considered. If another host is putting load on the SAN, it
could throw off the read timings and cause the filesystem driver to make
a bad guess.
Cheers,
Eric
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-05-12 16:14 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 [this message]
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=1178986457.6021.22.camel@eric-laptop \
--to=erpo41@gmail.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).