linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Derek Taubert <taubert@geeks.org>
To: Tejun Heo <htejun@gmail.com>
Cc: Derek Taubert <taubert@geeks.org>, linux-ide@vger.kernel.org
Subject: Re: Bad write performance with libata-tj-stable-2.6.17.4-20060710, pcmcia based sata_sil24, PMP, and NCQ drive
Date: Fri, 1 Sep 2006 10:24:35 -0700	[thread overview]
Message-ID: <20060901172435.GA26975@geeks.org> (raw)
In-Reply-To: <44F8365C.2020609@gmail.com>

On Fri, Sep 01, 2006 at 10:32:12PM +0900, Tejun Heo wrote:
> ># dd if=/dev/zero of=/dev/sda1 bs=4M count=512
> >
> >avg-cpu:  %user   %nice    %sys %iowait   %idle
> >           0.90    0.00    1.30   97.80    0.00
> >
> >Device:            tps    kB_read/s    kB_wrtn/s    kB_read    kB_wrtn
> >sda              15.00         0.00      1920.00          0      19200
> 
> Hmm... this really is weird.  FYI, you're the first to report such 
> problem.  As Jeff said, turning off write-back caching can have adverse 
> effect on write performance, but, then again, you previously reported 
> that the command queue is full.  Please update us on the write-back stuff.

>From searching the list archive, I gather this is controlled by "hdparm
-W"?

root@linux-srv:~ # hdparm -W 1 /dev/sda1                      

/dev/sda1:
 setting drive write-caching to 1 (on)
root@linux-srv:~ # dd if=/dev/zero of=/dev/sda1 bs=1M count=100
100+0 records in
100+0 records out
104857600 bytes (105 MB) copied, 53.8702 seconds, 1.9 MB/s
root@linux-srv:~ # hdparm -W 0 /dev/sda1                       

/dev/sda1:
 setting drive write-caching to 0 (off)
root@linux-srv:~ # dd if=/dev/zero of=/dev/sda1 bs=1M count=100
100+0 records in
100+0 records out
104857600 bytes (105 MB) copied, 53.7884 seconds, 1.9 MB/s

I'm going to try narrowing the scope of the test next.  Will purchase
an eSATA<->SATA cable today and try bypassing the port multiplier.

If that works, I'll try using one drive at a time on the PMP.

Thanks,
Derek

  reply	other threads:[~2006-09-01 17:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-28 23:01 Bad write performance with libata-tj-stable-2.6.17.4-20060710, pcmcia based sata_sil24, PMP, and NCQ drive Derek Taubert
2006-08-29  2:39 ` Tejun Heo
2006-08-29  4:58   ` Derek Taubert
2006-08-29  7:54     ` Derek Taubert
2006-08-29 13:35       ` Tejun Heo
2006-08-29 13:27     ` Tejun Heo
2006-08-29 16:44       ` Derek Taubert
2006-08-29 21:24         ` Jeff Garzik
2006-09-01 13:32         ` Tejun Heo
2006-09-01 17:24           ` Derek Taubert [this message]
2006-09-02  5:34             ` Derek Taubert
2006-09-03  6:26               ` Derek Taubert
2006-09-03 19:03                 ` Tejun Heo
2006-09-03 20:04                   ` Derek Taubert
2006-09-28 22:07                     ` Derek Taubert
2006-08-29 14:07   ` Greg Freemyer

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=20060901172435.GA26975@geeks.org \
    --to=taubert@geeks.org \
    --cc=htejun@gmail.com \
    --cc=linux-ide@vger.kernel.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).