For comparison with the SATA 150-6:
[EMAIL PROTECTED]:/home/ethant# bioctl -i ami0
Volume Status Size Device
ami0 0 Online 107374182400 sd0 RAID1
0 Online 160036814848 0:0.0 noencl < ST3160811AS 3.AA>
1 Online 160036814848 0:1.0 noencl < ST3160811AS 3.AA>
ami0 1 Online 42949672960 sd1 RAID1
0 Online 160036814848 0:0.0 noencl < ST3160811AS 3.AA>
1 Online 160036814848 0:1.0 noencl < ST3160811AS 3.AA>
ami0 2 Online 9712959488 sd2 RAID1
0 Online 160036814848 0:0.0 noencl < ST3160811AS 3.AA>
1 Online 160036814848 0:1.0 noencl < ST3160811AS 3.AA>
ami0 3 Hot spare 160036814848 0:2.0 noencl < ST3160811AS 3.AA>
[EMAIL PROTECTED]:/home/ethant# dd if=/dev/zero of=/dev/rsd1c bs=64k count=4096
4096+0 records in
4096+0 records out
268435456 bytes transferred in 6.441 secs (41674946 bytes/sec)
OpenBSD 4.0-beta (GENERIC) #1083: Mon Aug 21 21:24:02 MDT 2006
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: AMD Athlon(tm) XP 1800+ ("AuthenticAMD" 686-class, 256KB L2 cache)
1.54 GHz
cpu0:FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,
CMOV,PAT,PSE36,MMX,FXSR,SSE
real mem = 267939840 (261660K)
avail mem = 236683264 (231136K)
On 8/22/06, Marco Peereboom <[EMAIL PROTECTED]> wrote:
Due to the battery missing every IO the host sends has to complete before the
next one goes down. So the sequence of events is:
1. Send host io through driver
2. Firmware accepts it
3. Firmware creates 1 or more IOs and shoots those off to the disk
4. Firmware waits until IOs complete
5. Firmware raises interrupt to inform host that IO completed
6. ami(4) driver now completes the IO on the host
7. goto 1
Also if you want to test read/write performance you have to use the raw device.
A dd test should use for example /dev/rsd0c instead of a file.
Why don't you have a battery for that thing?
On a separate note; i do believe that LSI does have some firmware that'll allow
to enable write back cache without a battery. I am not 100% sure about though.
On Wed, Aug 23, 2006 at 04:01:10AM +0200, Robert Urban wrote:
> below are the results of my tests with the LSI MegaRAID SCSI 320-2
> controller on 3.9-release and 4.0-beta (snapshot pulled on Aug 22, 2006).
> I tested writing to both a RAID-5 and a RAID-0 logical drive. The
> RAID-0 drive consists of a single drive, what I'd call a JBOD. While
> the test program was running, I had iostat running, and I noted the
> results next to each test. The iostat values moved around a lot, so I
> took a figure close to the peak value.
>
> Naturally all the async tests were influenced by the buffer cache to
> a certain extent.
>
> I'm a little confused as to why writing sequential blocks with O_SYNC
> should be so slow...
