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: Tue, 29 Aug 2006 09:44:24 -0700 [thread overview]
Message-ID: <20060829164424.GA1603@geeks.org> (raw)
In-Reply-To: <44F440BE.80000@gmail.com>
On Tue, Aug 29, 2006 at 10:27:26PM +0900, Tejun Heo wrote:
> >>>2) hdparm -C for all 4 drives always shows "drive state is: standby"
> >>> even when I'm certain that the drives are active.
> >>hdparm -C says the same thing for my drive. I think it's safe to
> >>ignore. Hmmm... it needs to be tracked down. Maybe some problem in
> >>HDIO ioctl implementation in libata.
> >
> >It's a "nice to have" for using smartd. ie: don't spin the drives up to
> >poll the failure attributes, but they should be checked if the drive's
> >already active.
>
> I don't really understand what you mean. Can you elaborate?
Sure. See the "-n standby" option here:
http://smartmontools.sourceforge.net/man/smartd.conf.5.html
If the driver always reports "standby", then smartd effectively won't
monitor the device if "-n standby" is configured.
Now I can certainly eliminate the -n option from smartd.conf, but
then smartd will cause the drive(s) to spin up when it polls (see the
-p, -u, -t options).
> >>>I'd really like some assistance debugging the write performance issue.
> >>>The "hdparm -C" issue would be gravy...
> >>Please track down the reader.
> >
> >Before running dd (fuser -v /dev/sda1 shows nothing):
> [--snip--]
>
> Can you try 'dd if=/dev/zero of=/dev/sdX bs=4M count=1'?
Increasing the block size eliminates the reads (presumably because the
block driver doesn't have to fetch lines to read/modify/write), but the
write throughput is still very slow:
# 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
fd0 0.00 0.00 0.00 0 0
hda 0.20 0.80 0.00 8 0
md0 0.00 0.00 0.00 0 0
md1 0.00 0.00 0.00 0 0
sda 15.00 0.00 1920.00 0 19200
sdb 0.00 0.00 0.00 0 0
sdc 0.00 0.00 0.00 0 0
sdd 0.00 0.00 0.00 0 0
Compare that with:
# dd of=/dev/null if=/dev/sda1 bs=4M count=512
avg-cpu: %user %nice %sys %iowait %idle
0.50 0.00 78.10 21.40 0.00
Device: tps kB_read/s kB_wrtn/s kB_read kB_wrtn
fd0 0.00 0.00 0.00 0 0
hda 1.10 4.40 0.00 44 0
md0 0.00 0.00 0.00 0 0
md1 0.00 0.00 0.00 0 0
sda 426.70 51532.80 0.00 515328 0
sdb 0.00 0.00 0.00 0 0
sdc 0.00 0.00 0.00 0 0
sdd 0.00 0.00 0.00 0 0
Derek
next prev parent reply other threads:[~2006-08-29 16:44 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 [this message]
2006-08-29 21:24 ` Jeff Garzik
2006-09-01 13:32 ` Tejun Heo
2006-09-01 17:24 ` Derek Taubert
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=20060829164424.GA1603@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).