From: Petr Vandrovec <vandrove@vc.cvut.cz>
To: Richard Scobie <richard@sauce.co.nz>
Cc: linux-ide@vger.kernel.org
Subject: Re: Resets on sil3124 & sil3726 PMP
Date: Mon, 27 Aug 2007 00:11:39 -0700 [thread overview]
Message-ID: <46D2792B.401@vc.cvut.cz> (raw)
In-Reply-To: <46D2595B.1030409@sauce.co.nz>
Richard Scobie wrote:
> > 3726/4726 work very well under high load with most drives. I guess
> > you had some problem with the cage.
>
> Does anyone have any performance figures to share, with these PMP
> interfaces?
Hello,
what exactly you are looking for? For me it behaves exactly as
intended, and I did not notice any problems. When I communicate with
only one harddrive then performance is same as native. When I
communicate with more than one drive, then of course bandwidth between
host and PMP becomes bottleneck. /dev/sdf is using 1.5Gbps, everybody
else claims 3.0Gbps. Not that I see any difference :-(
Though I do not run any RAID on them (I would say that with PMP's
bottleneck it would be bad idea), so maybe I'm not stressing them
sufficiently to trip over bugs.
/dev/sda: 320GB Hitachi on sata_nv
/dev/sdb: 1TB Hitachi on sata_sil24 + 3726 (Sans Digital MS4UM)
/dev/sdc: 750GB Seagate on sata_sil24 + 3726
/dev/sdd: 1TB Hitachi on sata_sil24 + 3726
/dev/sde: 750GB Seagate on sata_sil24 + 3726
/dev/sdf: Sans Digital MS2UT with two 750GB in RAID1 on second sil24 port
gwy:~# for a in /dev/sd[abcdef]; do hdparm -t $a; done
/dev/sda:
Timing buffered disk reads: 214 MB in 3.01 seconds = 71.07 MB/sec
/dev/sdb:
Timing buffered disk reads: 236 MB in 3.00 seconds = 78.58 MB/sec
/dev/sdc:
Timing buffered disk reads: 220 MB in 3.02 seconds = 72.74 MB/sec
/dev/sdd:
Timing buffered disk reads: 240 MB in 3.02 seconds = 79.41 MB/sec
/dev/sde:
Timing buffered disk reads: 218 MB in 3.00 seconds = 72.64 MB/sec
/dev/sdf:
Timing buffered disk reads: 226 MB in 3.02 seconds = 74.95 MB/sec
Apparently 1TB Hitachis are slightly faster than 750GB Seagates...
gwy:~# hdparm -t /dev/sdb & hdparm -t /dev/sdd & sleep 20
(reformatted to show values in order, not interleaved)
/dev/sdd:
Timing buffered disk reads: 158 MB in 3.02 seconds = 52.40 MB/sec
/dev/sdb:
Timing buffered disk reads: 168 MB in 3.02 seconds = 55.68 MB/sec
gwy:~# hdparm -t /dev/sdc & hdparm -t /dev/sde & sleep 20
/dev/sde:
Timing buffered disk reads: 168 MB in 3.01 seconds = 55.89 MB/sec
/dev/sdc:
Timing buffered disk reads: 150 MB in 3.01 seconds = 49.77 MB/sec
gwy:~# hdparm -t /dev/sdb & hdparm -t /dev/sdc & hdparm -t /dev/sdd &
hdparm -t /dev/sde & sleep 20
/dev/sde:
Timing buffered disk reads: 98 MB in 3.02 seconds = 32.46 MB/sec
/dev/sdd:
Timing buffered disk reads: 100 MB in 3.06 seconds = 32.73 MB/sec
/dev/sdc:
Timing buffered disk reads: 92 MB in 3.07 seconds = 30.01 MB/sec
/dev/sdb:
Timing buffered disk reads: 118 MB in 3.05 seconds = 38.75 MB/sec
gwy:~# hdparm -t /dev/sdb & hdparm -t /dev/sdf & sleep 20
/dev/sdb:
Timing buffered disk reads: 194 MB in 3.02 seconds = 64.31 MB/sec
/dev/sdf:
Timing buffered disk reads: 224 MB in 3.02 seconds = 74.09 MB/sec
gwy:~# hdparm -t /dev/sda & hdparm -t /dev/sdb & hdparm -t /dev/sdc &
hdparm -t /dev/sdd & hdparm -t /dev/sde & hdparm -t /dev/sdf & sleep 20
/dev/sda:
Timing buffered disk reads: 200 MB in 3.03 seconds = 66.00 MB/sec
/dev/sdf:
Timing buffered disk reads: 220 MB in 3.05 seconds = 72.11 MB/sec
/dev/sde:
Timing buffered disk reads: 58 MB in 3.03 seconds = 19.12 MB/sec
/dev/sdd:
Timing buffered disk reads: 64 MB in 3.04 seconds = 21.06 MB/sec
/dev/sdb:
Timing buffered disk reads: 70 MB in 3.03 seconds = 23.10 MB/sec
/dev/sdc:
Timing buffered disk reads: 56 MB in 3.01 seconds = 18.59 MB/sec
gwy:~#
For comparsion 1TB Hitachi behind 3726 PMP (again MS4UM) with sata_sil
patch I sent last week (no NCQ, 1.5Gbps link between 3512 and PMP, and
3.0Gbps link between PMP and drive... why is it faster?):
petr-dev3:~# hdparm -t /dev/sdd
/dev/sdd:
Timing buffered disk reads: 248 MB in 3.01 seconds = 82.48 MB/sec
petr-dev3:~#
Petr
next prev parent reply other threads:[~2007-08-27 7:11 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-27 4:55 Resets on sil3124 & sil3726 PMP Richard Scobie
2007-08-27 7:11 ` Petr Vandrovec [this message]
2007-09-03 8:59 ` Tejun Heo
2007-09-03 9:57 ` Petr Vandrovec
2007-09-03 12:50 ` Tejun Heo
2007-09-04 1:38 ` Petr Vandrovec
2007-09-05 12:08 ` Petr Vandrovec
2007-09-05 21:30 ` Robin H. Johnson
2007-09-06 9:52 ` Petr Vandrovec
2007-09-06 18:02 ` Tejun Heo
2007-09-06 17:59 ` Tejun Heo
-- strict thread matches above, loose matches on Subject: below --
2007-09-03 19:39 Richard Scobie
2007-09-03 20:34 ` Robin H. Johnson
2007-09-03 21:21 ` Richard Scobie
2007-08-27 8:08 Richard Scobie
2007-08-27 22:49 ` Robin H. Johnson
2007-08-15 13:58 Rusty Conover
2007-08-17 18:06 ` Tejun Heo
2007-08-20 19:56 ` Rusty Conover
2007-08-21 2:42 ` Rusty Conover
2007-08-22 3:03 ` Tejun Heo
2007-08-22 5:00 ` Rusty Conover
2007-08-22 5:43 ` Tejun Heo
2007-08-22 6:11 ` Rusty Conover
2007-08-22 6:39 ` Tejun Heo
2007-08-22 6:56 ` Rusty Conover
2007-08-22 7:02 ` Tejun Heo
2007-08-22 7:49 ` Rusty Conover
2007-08-25 2:19 ` Tejun Heo
2007-08-26 16:37 ` Rusty Conover
2007-08-27 1:18 ` Tejun Heo
2007-08-14 23:39 Rusty Conover
2007-08-15 6:10 ` Tejun Heo
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=46D2792B.401@vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=linux-ide@vger.kernel.org \
--cc=richard@sauce.co.nz \
/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.