linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Lord <liml@rtr.ca>
To: Tomasz Chmielewski <mangoo@wpkg.org>
Cc: linux-ide@vger.kernel.org
Subject: Re: strange hdparm results with serverworks and pata-serverworks
Date: Wed, 25 Feb 2009 11:26:57 -0500	[thread overview]
Message-ID: <49A57151.1060206@rtr.ca> (raw)
In-Reply-To: <49A512ED.9080706@wpkg.org>

Tomasz Chmielewski wrote:
> Mark Lord schrieb:
> 
>> Everything looks configured correctly, so the only explanations
>> for the slow (10/20MB/sec) speeds are the CPU/RAM, or other system 
>> activity.
> 
> It's a pretty powerful machine with plenty of RAM, no other activity.
> 
> 
>> As for the disparity in initial throughput between the master/slave 
>> drives,
>> you could try reversing the two drives (swap them on the cable if using
>> "cable select", otherwise rejumper the master/slave setup).  Then see 
>> if the
>> slow start follows the specific drive to its new position on the cable,
>> or if the master ("a") drive is always slower.
> 
> Yes, "reversing" the drives makes the master slower (at least initially).
> 
> Controller's "feature"?
..

Kinda looks that way.  Perhaps the driver isn't setting the master device
up with optimal settings somewhere.. FIFO sizes or something ??

Maybe somebody more familiar with serverworks stuff could have a look now.


      reply	other threads:[~2009-02-25 16:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-23 20:37 strange hdparm results with serverworks and pata-serverworks Tomasz Chmielewski
2009-02-23 20:49 ` Greg Freemyer
2009-02-23 22:10   ` Tomasz Chmielewski
2009-02-24 13:29 ` Mark Lord
2009-02-24 18:37   ` Tomasz Chmielewski
2009-02-24 22:39     ` Mark Lord
2009-02-25  9:44       ` Tomasz Chmielewski
2009-02-25 16:26         ` Mark Lord [this message]

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=49A57151.1060206@rtr.ca \
    --to=liml@rtr.ca \
    --cc=linux-ide@vger.kernel.org \
    --cc=mangoo@wpkg.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).