From: Petr Vandrovec <vandrove@vc.cvut.cz>
To: "Robin H. Johnson" <robbat2@gentoo.org>
Cc: linux-ide@vger.kernel.org, Tejun Heo <htejun@gmail.com>,
Richard Scobie <richard@sauce.co.nz>
Subject: Re: Resets on sil3124 & sil3726 PMP
Date: Thu, 06 Sep 2007 02:52:48 -0700 [thread overview]
Message-ID: <46DFCDF0.6050107@vc.cvut.cz> (raw)
In-Reply-To: <20070905213006.GH22695@curie-int.orbis-terrarum.net>
Robin H. Johnson wrote:
> On Wed, Sep 05, 2007 at 05:08:00AM -0700, Petr Vandrovec wrote:
>>> 3124-2 (norco 4618):
>>> NCQ:
>>> 1TB alone: 82.30, 82.43
>>> 1TB+1TB: 68.36+68.25
>>> noNCQ:
>>> 1TB alone: 82.39, 82.29
>>> 1TB+1TB: 70.33+70.32, 69.47+70.01
>>> Unfortunately that enclosure has only two slots used. I'll try to not
>>> forget bring two more disks tomorrow to get it fully populated.
>> In case you are still follwing this thread, 3124-2 with 4 1TB drives
>> delivers 58.5MBps for each drive with NCQ enabled, and 60MBps with NCQ
>> disabled - total 235-240MBps read speed. I would like to see 320MBps, but
>> apparently today is not my lucky day...
> Just to confirm, how were you testing the multiple drive combination?
Concurrent hdparm -t, like
hdparm -t /dev/sdd & hdparm -t /dev/sde & hdparm -t /dev/sdf & hdparm -t
/dev/sdg & sleep 20
(and from hdparm output & visually confirmed that all activity LEDs go
on & off simultaneously)
So NCQ should not be able to show any (definitely not huge) benefits,
but there should not be any reason to not get 4x 1 drive speed as long
as neither PMP link nor PCI-X limits are hit.
Petr
next prev parent reply other threads:[~2007-09-06 9:52 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
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 [this message]
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=46DFCDF0.6050107@vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=richard@sauce.co.nz \
--cc=robbat2@gentoo.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.