public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Simon Koch <koch0121@umn.edu>
Cc: Ryan Geoffrey Bourgeois <rgb005@latech.edu>,
	linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: poor sata performance on 2.6
Date: Thu, 15 Apr 2004 21:03:49 -0400	[thread overview]
Message-ID: <407F30F5.1070305@pobox.com> (raw)
In-Reply-To: <407F1C07.6050104@umn.edu>

Simon Koch wrote:
> Ryan Geoffrey Bourgeois wrote:
>> 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

> 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.


Re-read his message.  He is using TX2, not SX4.

SX4 is vastly different.  Each request must bounce through a DIMM, which 
hurts performance.  Further, only one DIMM copy to/from system memory 
can be occuring at any one time, while you can be executing up to 4 ATA 
commands (one for each SATA port) in parallel.

SX4 performance currently suffers because of this bounce through the 
DIMM.  Two transactions, and two interrupts, are required for each disk 
transaction.

SX4 is really designed for RAID acceleration.  One may to improve 
performance (which I plan to implement) is using the DIMM as a 
write-through cache.

Another way to improve performance on SX4 is to have a special RAID 
driver which issues RAID1 or RAID5 reads and writes as a single 
transaction, thus maximizing the potential of the DIMM and cutting in 
_half_ the PCI bus bandwidth used for writes.  SX4, like other Promise 
products, can also offload RAID5 XOR calculations onto the hardware.

I _really_ like the SX4 -- it gives the programmer full control over all 
aspects of RAID operation, while providing useful hardware acceleration 
where it's needed.  And not getting in the way of the programmer, when 
it's not needed.

But currently, my libata driver does not use the advanced features, and 
so there is a performance hit.

	Jeff




  parent reply	other threads:[~2004-04-16  1:04 UTC|newest]

Thread overview: 30+ 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 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
2004-04-16  0:11         ` poor sata performance on 2.6 - Promise SX4 Ryan Geoffrey Bourgeois
2004-04-16  1:03         ` Jeff Garzik [this message]
2004-04-19 16:45           ` poor sata performance on 2.6 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=407F30F5.1070305@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox