public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jakob Østergaard" <jakob@unthought.net>
To: Martin Clausen <martin@ostenfeld.dk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Semi-OT] Dual Athlon support in kernel
Date: Fri, 27 Apr 2001 01:01:24 +0200	[thread overview]
Message-ID: <20010427010124.B14524@unthought.net> (raw)
In-Reply-To: <Pine.LNX.4.33.0104240115050.21785-100000@asdf.capslock.lan> <20010425011842.A3942@ostenfeld.dk>
In-Reply-To: <20010425011842.A3942@ostenfeld.dk>; from martin@ostenfeld.dk on Wed, Apr 25, 2001 at 01:18:42AM +0200

On Wed, Apr 25, 2001 at 01:18:42AM +0200, Martin Clausen wrote:
> On Tue, Apr 24, 2001 at 01:22:15AM -0400, Mike A. Harris wrote:
> > Also, what is a good rock solid SCSI RAID controller?  Money is
> > no object.  Reliability, performance and Linux compatibility are
> > though.
> 
> I have very good experiences with the Mylex controllers/drivers! 
> 
> But then again I also have good experiences with the new-style SW-RAID;
> it performs very well indead and it is quite cheap :) 

Remember, any RAID solution is based on software.  The difference is, whether
the software is closed-source and hiding on a slow processor, or free software
running on a much more powerful processor (which on the other hand also needs
to run other parts of the system, as this is the main CPU).

The main selling-points of software RAID except for stability and usually much
higher performance than "hardware" RAID is, that the interaction between the
userland tools and the RAID code is "open".   People who use RAID, be it one
kind or the other, occationally meet some problem where the RAID seems to be
having a will of it's own.  With the "open" solution, you as an administrator
actually have a chance of figuring out what happens.

I know the usual trouble-shooting on proprietary RAID seems to be "uh, it
doesn't work ?  well, try the newer drivers and firmware.  Oh, you did that,
well, then try the older versions then".   If people are comfortable with that
kind of systems, well, fine as long as it's not my data.   I want to know the
code I trust my data with.  From an theoretical point of view, it is stupid to
trust proprietary code - however, in the case of RAID I believe (at least some
of) the manufacturers has managed to prove that even from a purely pragmatic
point of view it is stupid to trust their code.

Yet, an awful lot of people seem to prefer the so-called "hardware" RAID  :)


-- 
................................................................
:   jakob@unthought.net   : And I see the elder races,         :
:.........................: putrid forms of man                :
:   Jakob Østergaard      : See him rise and claim the earth,  :
:        OZ9ABN           : his downfall is at hand.           :
:.........................:............{Konkhra}...............:

  reply	other threads:[~2001-04-26 23:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-24  5:22 [Semi-OT] Dual Athlon support in kernel Mike A. Harris
2001-04-24  6:05 ` Andrea Arcangeli
2001-04-24  7:33 ` Tom Leete
2001-04-24 10:18   ` Ville Herva
2001-04-24 10:39     ` Joseph Carter
2001-04-24 10:55       ` [Fully-OT] " Ville Herva
2001-04-24 11:11       ` [Semi-OT] " Andreas Jaeger
2001-04-24 23:18 ` Martin Clausen
2001-04-26 23:01   ` Jakob Østergaard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-04-24  6:03 Antwerpen, Oliver
2001-04-24  6:15 ` Andrea Arcangeli
2001-04-24  6:30   ` Miles Lane
2001-04-24  6:22 Antwerpen, Oliver

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=20010427010124.B14524@unthought.net \
    --to=jakob@unthought.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin@ostenfeld.dk \
    /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