All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Ryan Earl" <heretic@clanhk.org>
To: Daniel Brahneborg <daniel.com@wtnord.net>
Cc: linux-ide@vger.kernel.org
Subject: Re: siimage and two nics
Date: Sat, 27 Dec 2003 00:24:59 +0000	[thread overview]
Message-ID: <3FECD15B.1010004@clanhk.org> (raw)
In-Reply-To: <20031227083050.A8631@nettis.grimsta>

Daniel Brahneborg wrote:

>On Fri, Dec 26, 2003 at 05:42:20AM +0000, J. Ryan Earl wrote:
>  
>
>What matters is that I still want to be able to access the small
>IDE drive I have on the PATA connector.
>  
>
That should not be a problem.  If you build the via82cxxx into the 
kernel and use siimage as a module, the two sata drives should be hde 
and hdg, but you could build the siimage into the kernel and boot of the 
RAID if you wanted too.  Note, starting at A, every other hdX (ie hda, 
hdc, hde, hdg,...) will be a primary mastery.  Starting at B, every 
other hdX is a slave (hdb, hdd, hdf,...).  That's just the way the IDE 
layer handles names.  SATA doesn't have any slaves, it's all 1 disk per 
channel, point-to-point link, so you'll never see any of the "slave" 
harddrive names on a sata drive.  Check the dmesg and ls /proc/ide && 
cat /proc/hdX/model to see what your harddrives have been mapped to.  
Then setup your raidtab, fstab, and bootloader appropraitely.

>  
>
>>>Checking... oh, it's 1.06 in Linus 2.4.23 kernel.  The diff
>>>doesn't seem to be very much, just a check for 3114 and a fix
>>>for Seagate drives.
>>>      
>>>
>>Have you considered 2.6?
>>    
>>
>
>I tested it for a while, but had some problems with it.  I'll
>try it again and see if it makes any difference.
>  
>
I suggest the -mm tree, it includes all the patches for the siimage 
driver, plus many more.  It has been stable in my testing.

>How do I find out what happens with the PATA disk when I load the
>siimage module?
>  
>
See above.

>Btw, what speed should I be able to get with the siimage module?
>  
>
You have to consider I'm using WD360GD "Raptors" and not whatever drive 
you have.  I get 35-55 MB/sec sequential read/write throughput on a 
single disk.  I tested RAID0 and RAID1 on the siimage 3112A (btw A = 
revision 2).  In RAID0, I'm getting about 75MB/sec sequential read/write 
performance (Testbed = AthlonXP 1800 1.53Ghz, 512MB CL2 DDR).  I've seen 
others using this disk off their Southbridge--no 32bit/33MHz PCI 
bottleneck--get 100MB/sec on these with RAID0.  I think bus-speed 
somehow affects RAID0 performance especially with 16MB of coolective 
cache on the RAID drives.  RAID1 looks a lot better though.  I get 
~50MB/sec write--essentially the same as with one disk and in agreement 
with manufacturer's performance claims.  Remember it's writing to both 
disks at once, so really 100MB/s is going across the 133MB/s PCI bus.  A 
single sequential read tops out around 55MB/sec.  However, I can sustain 
2 parallel sequential reads, both at ~50MB/s so I get an aggregate of 
100+MB/s sequential read throughput with RAID1-mirroring.  
Unfortunately, RAID0 also slightly lowered the average number of seeks 
per interval while raising the avereage seek time over a single 
non-RAID'd disk.  RAID1, on the otherhand, increased the average number 
of seeks per interval by 80% over one disk (roughly ~200 seeks/s to 360 
seeks/s) and it lowered avereage seek time 10-50% on reads.  Hello 
database that's answers queries that are 70% SELECT statements.

RAID1 is absolutely perfect for my needs, this will dramatically 
increase my I/O capabilities .  I can't quote you any RAID5 results. 

-ryan


  reply	other threads:[~2003-12-27 18:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-26  7:54 siimage and drive order problem Daniel Brahneborg
2003-12-26 13:14 ` Ryan Earl
2003-12-26 18:57   ` siimage and two nics (was: drive order problem) Daniel Brahneborg
2003-12-26  3:48     ` siimage and two nics J. Ryan Earl
2003-12-26 22:28       ` Daniel Brahneborg
2003-12-26  5:42         ` J. Ryan Earl
2003-12-27  7:30           ` Daniel Brahneborg
2003-12-27  0:24             ` J. Ryan Earl [this message]
2003-12-27 22:40               ` Daniel Brahneborg
2003-12-28 14:49               ` Daniel Brahneborg

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=3FECD15B.1010004@clanhk.org \
    --to=heretic@clanhk.org \
    --cc=daniel.com@wtnord.net \
    --cc=linux-ide@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 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.