From: Nuno Silva <nuno.silva@vgertech.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Lincoln Dale <ltd@cisco.com>,
Ian.Godin@lowrydigital.com, linux-kernel@vger.kernel.org
Subject: Re: Drive performance bottleneck
Date: Sun, 06 Feb 2005 04:25:42 +0000 [thread overview]
Message-ID: <42059C46.1080406@vgertech.com> (raw)
In-Reply-To: <20050204150728.6a697e0e.akpm@osdl.org>
Andrew Morton wrote:
> Lincoln Dale <ltd@cisco.com> wrote:
>
>>sg_dd uses a window into a kernel DMA window. as such, two of the four
>>memory acccesses are cut out (1. DMA from HBA to RAM, 2. userspace
>>accessing data).
>>1.6Gbps / 2 = 800MB/s -- or roughly what Ian was seeing with sg_dd.
>
>
> Right. That's a fancy way of saying "cheating" ;)
>
> But from the oprofile output it appears to me that there is plenty of CPU
> capacity left over. Maybe I'm misreading it due to oprofile adding in the
> SMP factor (25% CPU on a 4-way means we've exhausted CPU capacity).
sg_dd is lying or /dev/sg* is broken. Try to do that sg_dd test in any
single drive and you'll get 20 times the performance you're supposed to
achieve:
puma:/tmp/dd# time sg_dd if=/dev/sg1 of=/dev/null bs=64k count=1000000
time=1
Reducing read to 64 blocks per loop
time to transfer data was 69.784784 secs, 939.12 MB/sec
1000000+0 records in
1000000+0 records out
This is a single sata drive. I'm lucky, am I not? ;-)
Regards,
Nuno Silva
prev parent reply other threads:[~2005-02-06 4:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-03 2:24 Drive performance bottleneck Ian Godin
2005-02-03 3:56 ` Bernd Eckenfels
2005-02-03 16:49 ` Ian Godin
2005-02-03 16:06 ` Jens Axboe
2005-02-03 17:40 ` Nuno Silva
2005-02-03 18:08 ` Ian Godin
2005-02-03 19:03 ` Paulo Marques
2005-02-04 19:36 ` Andy Isaacson
2005-02-04 9:32 ` Andrew Morton
2005-02-04 22:51 ` Lincoln Dale
2005-02-04 23:07 ` Andrew Morton
2005-02-06 4:25 ` Nuno Silva [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=42059C46.1080406@vgertech.com \
--to=nuno.silva@vgertech.com \
--cc=Ian.Godin@lowrydigital.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltd@cisco.com \
/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.