linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stan Hoeppner <stan@hardwarefreak.com>
To: Benjamin ESTRABAUD <be@mpstor.com>
Cc: Roberto Spadim <rspadim@gmail.com>, Drew <drew.kay@gmail.com>,
	Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: Best configuration for bcache/md cache or other cache using ssd
Date: Thu, 19 Sep 2013 18:22:53 -0500	[thread overview]
Message-ID: <523B874D.4050904@hardwarefreak.com> (raw)
In-Reply-To: <523B3185.3020309@mpstor.com>

On 9/19/2013 12:16 PM, Benjamin ESTRABAUD wrote:

> MegaRAID is the LSI RAID controller's driver/management software name.

For the young pups here, MegaRAID was the brand name for the hardware
RAID products sold by American Megatrends Incorporated, AMI, in the
1990s.  You just might recognize that name, since most PCs ship with AMI
BIOS.  AMI sold their RAID division to LSI more than 10 years ago.  They
also sold their motherboard division though I can't recall to whom.

LSI also purchased Mylex Corp around the same time frame.  Together, AMI
and Mylex owned over ~70% of the US RAID card market, a large percent of
the worldwide RAID card market, and had OEM contracts with all of the
major hardware vendors, including Bull, Data General, DEC, Dell,
Fujitsu/Siemens, HP, IBM, SGI, SUN, Unisys, etc.  Sometime later they
also acquired 3Ware, pretty well sewing up the market.

Mylex didn't use any branding, simply model numbers, such as DAC960,
DAC1100, etc.  So LSI retained the MegaRAID brand and has used it for
all RAID products to date, as it had wide recognition and is catchy as
far as branding goes.

-- 
Stan


  parent reply	other threads:[~2013-09-19 23:22 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-17 19:20 Best configuration for bcache/md cache or other cache using ssd Roberto Spadim
2013-09-18 13:59 ` Drew
     [not found]   ` <CAH3kUhHin5PfjDCNFjD8eypNML=0YrkQp14DrCADc2StcODdaw@mail.gmail.com>
2013-09-18 15:39     ` Fwd: " Drew
2013-09-18 16:00       ` Mark Knecht
2013-09-18 15:51     ` Fwd: " Roberto Spadim
2013-09-18 16:07       ` Tommy Apel
     [not found]         ` <CAH3kUhEWUe=20ovmd5BT3kzmYn25YS3Np5R3jPiJDBEAhAOb_A@mail.gmail.com>
2013-09-18 16:27           ` Tommy Apel
2013-09-18 17:15       ` Drew
2013-09-18 17:33         ` Roberto Spadim
2013-09-19  2:26           ` Stan Hoeppner
2013-09-19  3:42             ` Roberto Spadim
2013-09-19  7:47               ` Stan Hoeppner
2013-09-19 15:30                 ` Roberto Spadim
2013-09-19 15:49                   ` Benjamin ESTRABAUD
2013-09-19 16:23                     ` Roberto Spadim
2013-09-19 16:31                       ` Benjamin ESTRABAUD
     [not found]                         ` <CAH3kUhE33h=7D6r7KO9VvQRN5qrZS+cad KUBQW8POFYvyGsS3w@mail.gmail.com>
     [not found]                           ` <523B3185.3020309@mpstor.com>
2013-09-19 23:22                             ` Stan Hoeppner [this message]
2013-09-24  5:06                               ` Roberto Spadim
2013-09-24  6:11                                 ` Roberto Spadim
2013-09-24  7:18                                   ` Tommy Apel
2013-09-24  8:29                                 ` Stan Hoeppner
2013-09-24 12:12                                   ` Bradley D. Thornton
2013-09-25  2:32                                     ` Stan Hoeppner
2013-09-25  2:44                                       ` Stan Hoeppner
2013-09-25  4:35                                       ` Roberto Spadim
2013-09-25  5:53                                         ` Stan Hoeppner
2013-09-19 22:15                   ` Stan Hoeppner
2013-09-19 22:50                     ` Roberto Spadim

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=523B874D.4050904@hardwarefreak.com \
    --to=stan@hardwarefreak.com \
    --cc=be@mpstor.com \
    --cc=drew.kay@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=rspadim@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;
as well as URLs for NNTP newsgroup(s).