linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Jeb Thomson <jet00159@outlook.com>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Single disk parrallelization
Date: Fri, 19 Sep 2014 14:47:39 -0400	[thread overview]
Message-ID: <541C7A4B.6060502@gmail.com> (raw)
In-Reply-To: <BLU406-EAS1974279D81BF03735D65B479AB40@phx.gbl>

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

On 2014-09-19 14:10, 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...
>
In theory this is a great idea except for two things:
1) Most consumer drives have only one platter.
2) The kernel doesn't have such low-level hardware access, so it would 
have to be implemented in device firmware (and I'd be willing to bet 
that most drive manufacturers already stripe data across multiple 
platters when possible).



[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 2455 bytes --]

  reply	other threads:[~2014-09-19 18:47 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 [this message]
2014-09-19 21:29 ` Ralf-Peter Rohbeck
2014-09-24 21:09 ` Calvin Walton

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=541C7A4B.6060502@gmail.com \
    --to=ahferroin7@gmail.com \
    --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).