linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roman Mamedov <rm@romanrm.ru>
To: stan@hardwarefreak.com
Cc: "Joachim Otahal (privat)" <Jou@gmx.net>, linux-raid@vger.kernel.org
Subject: Re: RAID5 with two drive sizes question
Date: Wed, 6 Jun 2012 10:16:27 +0600	[thread overview]
Message-ID: <20120606101627.5cf8ecbc@natsu> (raw)
In-Reply-To: <4FCE6DCD.7030207@hardwarefreak.com>

[-- Attachment #1: Type: text/plain, Size: 1600 bytes --]

On Tue, 05 Jun 2012 15:36:29 -0500
Stan Hoeppner <stan@hardwarefreak.com> wrote:

> > Except this would not make any sense even as a thought experiment. You don't
> > want a configuration where two or more areas of the same physical disk need to
> > be accessed in parallel for any read or write to the volume. And it's pretty
> > easy to avoid that.
> 
> You make a good point but your backing argument is incorrect:  XFS by
> design, by default, writes to 4 equal sized regions of a disk in parallel.

I said: "...need to be accessed in parallel for any read or write".

With XFS you mean allocation groups, however I don't think that if you write
any large file sequentially to XFS, it will always cause drive's head to jump
around between four areas because the file is written "in parallel", striped
to four different locations, which is the main problem that we're trying to
avoid.

XFS allocation groups are each a bit like an independent filesystem, to allow
for some CPU- and RAM-access-level parallelization. However spinning devices
and even SSDs can't really read or write quickly enough "in parallel", so
parallel access to different areas of the same device is used in XFS not for
*any read or write*, but only in those cases where that can be beneficial for
performance -- and even then, likely managed carefully either by XFS or by
lower level of I/O schedulers to minimize head movements.

-- 
With respect,
Roman

~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Stallman had a printer,
with code he could not see.
So he began to tinker,
and set the software free."

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2012-06-06  4:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-05 17:27 RAID5 with two drive sizes question Joachim Otahal (privat)
2012-06-05 17:39 ` Roman Mamedov
2012-06-05 19:41   ` Joachim Otahal (privat)
2012-06-05 19:59     ` Roman Mamedov
2012-06-05 20:36       ` Stan Hoeppner
2012-06-05 20:48         ` Joachim Otahal (privat)
2012-06-06  4:16         ` Roman Mamedov [this message]
2012-06-07  0:39           ` Stan Hoeppner

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=20120606101627.5cf8ecbc@natsu \
    --to=rm@romanrm.ru \
    --cc=Jou@gmx.net \
    --cc=linux-raid@vger.kernel.org \
    --cc=stan@hardwarefreak.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).