From: Dave Hansen <haveblue@us.ibm.com>
To: walter <walt@nea-fast.com>
Cc: linux-kernel@vger.kernel.org, davis@jdhouse.org,
Gerrit Huizenga <gerrit@us.ibm.com>
Subject: Re: oracle rmap kernel version
Date: Wed, 13 Mar 2002 13:11:01 -0800 [thread overview]
Message-ID: <3C8FC065.4060904@us.ibm.com> (raw)
In-Reply-To: <794826DE8867D411BAB8009027AE9EB913D03D23@FMSMSX38> <3C8FAB25.1080706@us.ibm.com> <200203132056.PAA04508@int1.nea-fast.com>
walter wrote:
> Not sure right off the top of my head. I'm planning on using 2 controllers,
> each from a different manufactures. My reasoning behind this is two fold.
> Number one is in case a "bug" creeps up with one of the drivers I can still
> string all the drives off the other controller. Performance will decrease,
> but I'd rather be slow than dead in the water. The second reason is the
> probability of both controllers failing (hardware) at same time due to a bad
> chip batch at the manufacture. Do you have any suggestions on controllers?
> Adaptec and IBM (not sure which models) ?
I haven't done any of the testing myself. But, I was told that the
Adaptec AIC stuff is good. I think that the LSE patch has been tested
on with Adaptec (aic7xxx) and QLogic fiber channel controllers. I guess
that the QLogic stuff is liked because the drivers are open source.
I was surprised to see that the ServeRAID driver isn't touched by the
lse patch. I thought that it still uses the io_request_lock in 2.4.
Care to add anything, Gerrit?
--
Dave Hansen
haveblue@us.ibm.com
next prev parent reply other threads:[~2002-03-13 21:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-12 20:04 oracle rmap kernel version Chen, Kenneth W
2002-03-13 19:40 ` Dave Hansen
2002-03-13 20:56 ` walter
2002-03-13 21:11 ` Dave Hansen [this message]
2002-03-13 22:27 ` Gerrit Huizenga
-- strict thread matches above, loose matches on Subject: below --
2002-03-12 17:29 walter
2002-03-12 18:06 ` Martin J. Bligh
2002-03-12 18:34 ` Jonathan A. Davis
2002-03-13 6:03 ` Jauder Ho
2002-03-13 17:10 ` Alan Cox
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=3C8FC065.4060904@us.ibm.com \
--to=haveblue@us.ibm.com \
--cc=davis@jdhouse.org \
--cc=gerrit@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=walt@nea-fast.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.