linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Calvin Walton <calvin.walton@kepstin.ca>
To: Tomasz Torcz <tomek@pipebreaker.pl>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: SSD format/mount parameters questions
Date: Fri, 18 May 2012 12:09:08 -0400	[thread overview]
Message-ID: <1337357348.7927.5.camel@ayu> (raw)
In-Reply-To: <20120518153258.GE24598@mother.jarsat.pl>

On Fri, 2012-05-18 at 17:32 +0200, Tomasz Torcz wrote:
> On Fri, May 18, 2012 at 05:08:33PM +0200, Clemens Eisserer wrote:
> > > I would not buy anything else
> > > than intel. I have about 26 of them for years now (both in servers and
> > > workstations, several series), and never had an issue. Two of my
> > > colleagues have OCZ, and both had to RMA them.
> > 
> > I guess it boils down wether you want intel also to rule the SSD
> > market in the long term, as they do with PC processors...
> > 
> > Comparing intel SSDs with OCZ is not that fair, as OCZ has always been
> > low-priced bleeding edge stuff.
> 
>   Looking into the controllers...
>   first there were bunch of different ones; Intel had it own design with
> SSD 320.
>   Then come Sandforce; it got broadly used, despite sucking when used
> with FDE. Even Intel started to used Sandforce - SSD 520. How's
> reliabilty of Intel differs?
>   Latest fad is Marvell controller; again Intel joins the pack with SSD510.
> 
>   So, Intel is not that different anymore.

The controllers themselves really aren't that interesting any more - an
SSD controller is really just an ARM or MIPS core with some flash
interfaces, a SATA interface, and some ram - running proprietary
firmware.

Several of the Marvell devices actually have completely different
firmwares (e.g. Intel's firmware for Marvell devices was reportedly
developed by them in-house), and Intel's Sandforce firmware has some
customizations for improved reliability, at the expense of some speed.

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


  reply	other threads:[~2012-05-18 16:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-17 14:45 SSD format/mount parameters questions Martin
2012-05-18  7:02 ` Sander
2012-05-18 15:08   ` Clemens Eisserer
2012-05-18 15:32     ` Tomasz Torcz
2012-05-18 16:09       ` Calvin Walton [this message]
2012-05-19 17:36   ` Martin Steigerwald
2012-05-22 21:30     ` Martin

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=1337357348.7927.5.camel@ayu \
    --to=calvin.walton@kepstin.ca \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=tomek@pipebreaker.pl \
    /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).