From: Calvin Walton <calvin.walton@kepstin.ca>
To: Jeb Thomson <jet00159@outlook.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Single disk parrallelization
Date: Wed, 24 Sep 2014 17:09:24 -0400 [thread overview]
Message-ID: <1411592964.22432.1.camel@kepstin.ca> (raw)
In-Reply-To: <BLU406-EAS1974279D81BF03735D65B479AB40@phx.gbl>
On Fri, 2014-09-19 at 13:10 -0500, Jeb Thomson wrote:
> With the advanced features of btrfs, it would be an additional
> simple task to make different platters run in parallel.
>
> In this case, say a disk has three platters, and so three seek heads
> as well. If we can identify that much, and what offsets they are at,
> it then becomes a trivial matter to place the reads and writes to
> different platters at the same time.
>
> In affect, this means each platter should be operating as a single
> virtualized unit, instead of one single unit...
>
If you look at a disk benchmark of a modern multi-platter drive, e.g.
http://www.anandtech.com/show/8265/wd-red-pro-review-4-tb-drives-for-nas-systems-benchmarked/4
(All of the drives in this review have 4 or 5 platters)
You'll see that the performance is a fairly smooth curve down from max
speed (outer edge of the platters) to min speed (inner edge of the
platters).
Since this is a smooth curve, rather than starting high, going down,
then starting high on the next platter and going down again, this
means that the drive controller is already writing to all of the
platters at the same time - or at the very least, writing in a striped
pattern between platters without moving the seek heads. There's
nothing you could do at the OS level which would make it faster
(besides preferring to read and write at the lower LBAs of the drive).
--
Calvin Walton <calvin.walton@kepstin.ca>
prev parent reply other threads:[~2014-09-24 21:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-19 18:10 Single disk parrallelization Jeb Thomson
2014-09-19 18:47 ` Austin S Hemmelgarn
2014-09-19 21:29 ` Ralf-Peter Rohbeck
2014-09-24 21:09 ` Calvin Walton [this message]
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=1411592964.22432.1.camel@kepstin.ca \
--to=calvin.walton@kepstin.ca \
--cc=jet00159@outlook.com \
--cc=linux-btrfs@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).