linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Daniel Brahneborg <daniel.com@wtnord.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: Status of Promise drivers?
Date: Tue, 30 Dec 2003 14:06:41 -0500	[thread overview]
Message-ID: <3FF1CCC1.3050304@pobox.com> (raw)
In-Reply-To: <20031230200012.C14399@nettis.grimsta>

Daniel Brahneborg wrote:
> Hi,
> 
> I'm having serious problems with my Silicon Image SATA card,
> and am considering replacing with a (more expensive) Promise
> SATA TX2 Plus card.
> 
> First I have some questions, to avoid getting into the same
> mess as I'm in now.
> 
>  1. What is the status of the Promise driver?  Stable for
>     everybody? (The SI3112 has problems for some people when
>     using the IDE driver, and for some with the SCSI driver.)
>     A binary module is ok, a binary bzImage definately is not.

It's beta, and stable.


>  2. Has anybody used the driver on an Abit KV7 motherboard?
> 
>  3. Has anybody used it with *2* network cards?  Bonus
>     points for the builtin Via Rhine and an 8139 card.
>     (The SCSI driver for the SI3112 kills the machine when a
>     second card is activated.)
> 
>  4. Has anybody used it together with two other disks on the
>     VIA SATA interface on the KV7?
> 
>  5. Has anybody used it for a Raid5 setup? (With SI3112 Raid1
>     works better than Raid5, since Raid5 gives corrupted files
>     all over the place and Raid1 only corrupts them once in
>     a while.)

Any comparison with Silicon Image is false.  The Silicon Image driver 
has been repeatedly stated (by me, the author) to be BROKEN.  It is 
thusly marked with CONFIG_BROKEN.

Those who ignore the author stating the Silicon Image driver is _alpha_ 
and unfinished do so at their own risk.


>  6. Has anybody used it in a non-root setup, having hda on
>     the PATA interface?  (The SI3112 causes lots of problems
>     with I/O port and IRQ conflicts, requiring hours of
>     tweaking of the boot parameters.)

PATA interfaces on Promise SATA are not yet supported.


>  7. Do you have DMA enabled?  (SI3112 without DMA works fine,
>     but with terrible performance.)

DMA cannot be disabled :)


>  8. Do you get decent performance? (The 5MB/sec I get without
>     DMA on the SI3112 card is _not_ decent.)

Performance is far beyond this.

	Jeff





  reply	other threads:[~2003-12-30 19:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-30 19:00 Status of Promise drivers? Daniel Brahneborg
2003-12-30 19:06 ` Jeff Garzik [this message]
2003-12-30 19:24   ` Daniel Brahneborg
2003-12-30 19:57     ` Jeff Garzik
2003-12-30 20:18       ` Daniel Brahneborg
2003-12-30 20:25         ` Jeff Garzik
2003-12-30 20:38           ` Daniel Brahneborg
2003-12-30 23:38             ` Jeff Garzik
2004-01-10 15:14           ` Daniel Brahneborg
2003-12-30 20:21       ` Hendrik Visage
2003-12-30 20:27         ` Jeff Garzik
2004-02-03 18:23   ` Daniel Brahneborg
2004-02-04 15:02     ` Gunnlaugur Thor Briem
2004-02-06 21:13       ` Gunnlaugur Thor Briem
2003-12-30 23:21 ` Status of HighPoint / " Daniel Brahneborg
2003-12-30 23:37   ` Jeff Garzik
2003-12-30 23:55     ` jlewis

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=3FF1CCC1.3050304@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=daniel.com@wtnord.net \
    --cc=linux-raid@vger.kernel.org \
    /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).