Re: satalink(4) on sparc64

Martin Husemann <[email protected]>
Newsgroups gmane.os.netbsd.ports.sparc64
Message-ID <[email protected]>
I have:

siisata0 at pci1 dev 2 function 0: CMD Technology SiI3124 SATALink (rev. 0x02)
siisata0: interrupting at ivec 744
siisata0: SiI3124, 3.0Gb/s
siisata0: 32-bit 66MHz PCI
atabus0 at siisata0 channel 0
atabus1 at siisata0 channel 1
atabus2 at siisata0 channel 2
atabus3 at siisata0 channel 3
siisata0 port 0: device present, speed: 3.0Gb/s
siisata0 port 1: device present, speed: 3.0Gb/s
wd0 at atabus0 drive 0
wd0: <TOSHIBA HDWE160>
wd0: drive supports 16-sector PIO transfers, LBA48 addressing
wd0: 5589 GB, 11628021 cyl, 16 head, 63 sec, 512 bytes/sect x 11721045168 sectors
[..]
wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 5 (Ultra/100), WRITE DMA FUA, NCQ (32 tags)
wd0(siisata0:0:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 5 (Ultra/100) (using DMA), NCQ (30 tags)
wd1 at atabus1 drive 0
wd1: <Samsung SSD 850 PRO 256GB>
wd1: drive supports 1-sector PIO transfers, LBA48 addressing
wd1: 238 GB, 496149 cyl, 16 head, 63 sec, 512 bytes/sect x 500118192 sectors
[..]
wd1: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133), WRITE DMA FUA, NCQ (32 tags)
wd1(siisata0:1:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133) (using DMA), NCQ (30 tags)

This is on a SunBlade 2500 running -current. The use_ncq sysctl nodes are
all 1.

When writing to the raw device on the real hard disk:

[/tmp] whoever-brings-the-night # dd if=/dev/zero bs=1m count=1000 of=/dev/rdk5
1000+0 records in
1000+0 records out
1048576000 bytes transferred in 8.891 secs (117936790 bytes/sec)

When writing to the swap partition on the SSD:

[/tmp] whoever-brings-the-night # dd if=/dev/zero bs=1m count=1000 of=/dev/rdk2
1000+0 records in
1000+0 records out
1048576000 bytes transferred in 8.587 secs (122112029 bytes/sec)

Both devices have write-back cache enabled (this machine has a UPS).

Martin
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.