public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Calvin Walton <calvin.walton@kepstin.ca>
To: Tom Yan <tom.ty89@gmail.com>, Duncan <1i5t5.duncan@cox.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: multiple "devices" with multiple partitions on one SSD
Date: Mon, 15 Jun 2015 12:07:17 -0400	[thread overview]
Message-ID: <1434384437.6916.11.camel@kepstin.ca> (raw)
In-Reply-To: <CAGnHSE=ik7Vta4i3ia9AvH=Epb=G3oifCAvTJVck81zi=0VWjQ@mail.gmail.com>

On Fri, 2015-06-12 at 18:11 +0800, Tom Yan wrote:
> Thank you for you reply. I thought of the same thing as you've told,
> but because I don't really know how SSD/SATA works internally, so I
> was also thinking if "raid0" on the same drive might works as
> something like "Hyper-Threading" in CPU.

Modern SSD controllers are already effectively doing "RAID0" striping
over multiple individual flash chips inside the drive in order to
achieve maximum sequential write speeds. With high end drives, a single
sequential write can already saturate the available bandwidth on the
SATA wire.

If anything, splitting up writes to bounce back and forth between two
different regions of the same drive would add overhead, and might
disrupt the write optimizations in the drive controller. It would
probably end up slower - although the difference might not be noticable

If you're just looking for speed, stick to single mode and let the
drive go fast.

Calvin.

-- 
Calvin Walton <calvin.walton@kepstin.ca>

      reply	other threads:[~2015-06-15 16:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-11 11:34 multiple "devices" with multiple partitions on one SSD Tom Yan
2015-06-12  9:47 ` Duncan
2015-06-12 10:11   ` Tom Yan
2015-06-15 16:07     ` 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=1434384437.6916.11.camel@kepstin.ca \
    --to=calvin.walton@kepstin.ca \
    --cc=1i5t5.duncan@cox.net \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=tom.ty89@gmail.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