All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Koch <koch0121@umn.edu>
To: Ryan Geoffrey Bourgeois <rgb005@latech.edu>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: poor sata performance on 2.6
Date: Thu, 15 Apr 2004 18:34:31 -0500	[thread overview]
Message-ID: <407F1C07.6050104@umn.edu> (raw)
In-Reply-To: <1082044297.407eaf894ddda@webmail.LaTech.edu>

Ryan Geoffrey Bourgeois wrote:

>>I'm almost ready to buy separate controller, but all that I could find nearby
>>
>>are based on the same Silicon Image chipset
>>
>>    
>>
>
>I do recomend Promise's SATA controller cards.  The kernel drivers are excellent
>imho.  As well as my onboard Promise TX2, I'm using a thei S150 SX4 RAID5
>capable controller in my file server.  A controlle ard should be easy enough to
>finnd online.  I shop at NewEgg.com.  Good prices, highly rcommended.
>
>I'm gonna take a look at your .config as soon as I get back to my own computer.
>
>Cheers.
>-Ryan
>
>-------------------------------------------------
>This mail sent through IMP: http://horde.org/imp/
>

What kernel/driver are you using for the S150 SX4?  I couldn't ever get 
better than 13MB/sec from it in 2.6.  Of course, the last I tried was 
2.6.3.  I could get 55MB/sec using 2.4 and Promise's partial source 
driver, but since my onboard SATA controller works fine in 2.6 I'm just 
using that meanwhile.

Thanks,
    Simon

  reply	other threads:[~2004-04-15 23:34 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-14 22:36 poor sata performance on 2.6 Konstantin Sobolev
2004-04-15  3:54 ` Ryan Geoffrey Bourgeois
2004-04-15 10:55   ` Konstantin Sobolev
2004-04-15 12:02     ` Justin Cormack
2004-04-15 13:34       ` Konstantin Sobolev
2004-04-15 14:00         ` Justin Cormack
2004-04-15 14:26           ` Konstantin Sobolev
2004-04-15 14:33             ` Justin Cormack
2004-04-15 14:48               ` Konstantin Sobolev
2004-04-15 14:52                 ` Prakash K. Cheemplavam
2004-04-15 15:08                 ` Justin Cormack
2004-04-15 15:16                   ` Konstantin Sobolev
2004-04-23  4:50                   ` Jeremy Higdon
2004-04-15 17:30                 ` Denis Vlasenko
2004-04-16  1:05                   ` Jeff Garzik
2004-04-16 14:48                     ` Denis Vlasenko
2004-04-16 16:59                       ` Konstantin Sobolev
2004-04-16 17:46                       ` cira
2004-04-20 12:41                     ` Prakash K. Cheemplavam
2004-04-15 15:51     ` Ryan Geoffrey Bourgeois
2004-04-15 23:34       ` Simon Koch [this message]
2004-04-16  0:11         ` poor sata performance on 2.6 - Promise SX4 Ryan Geoffrey Bourgeois
2004-04-16  1:03         ` poor sata performance on 2.6 Jeff Garzik
2004-04-19 16:45           ` Henrik Gustafsson
2004-04-19 16:56             ` Jeff Garzik
2004-04-15  7:12 ` Lenar Lõhmus
2004-04-15 10:40   ` Konstantin Sobolev
2004-04-15 12:37     ` Denis Vlasenko
2004-04-15 12:57       ` Lenar Lõhmus
2004-04-15 16:54         ` Denis Vlasenko
2004-04-15 13:05       ` Konstantin Sobolev
2004-04-15 19:50 ` Pavel Machek
2004-04-15 21:13   ` Konstantin Sobolev

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=407F1C07.6050104@umn.edu \
    --to=koch0121@umn.edu \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rgb005@latech.edu \
    /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.