mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: "Martin A. Fink" <fink@mpe.mpg.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: SATA Performance with Intel ICH6
Date: Sat, 25 Nov 2006 11:23:21 -0800	[thread overview]
Message-ID: <20061125112321.1767a53c.akpm@osdl.org> (raw)
In-Reply-To: <200611241510.11526.fink@mpe.mpg.de>

On Fri, 24 Nov 2006 15:10:11 +0100
"Martin A. Fink" <fink@mpe.mpg.de> wrote:

> Here some measurement results:
> 
> time dd if=/dev/zero of=test.zero bs=1M count=1000
> results in
> 
> real 0m52.561s
> user 0m0.003s
> sys  0m7.407s
> 
> and strace dd... gives among other information
> 6.84s 1004calls syscall: write
> 
> So I spend 45s of 52s within the kernel. Why so long?

Profiling the kernel will tell.  Preferably with oprofile, but if for some
reason that doesn't work, with the old profiler.

I use this:

#!/bin/sh
sudo opcontrol --stop
sudo opcontrol --shutdown
sudo rm -rf /var/lib/oprofile
sudo opcontrol --vmlinux=/boot/vmlinux-$(uname -r)
sudo opcontrol --start-daemon
sudo opcontrol --start
time $@
sudo opcontrol --stop
sudo opcontrol --shutdown
sudo opreport -l /boot/vmlinux-$(uname -r) | head -50

I have seen PIO and MMIO operations on PCI busses take tremendous amounts
of time when that bus is saturated with DMA transfers.  But that was back
in the old days.

  parent reply	other threads:[~2006-11-25 19:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-24 13:07 Martin A. Fink
2006-11-24 13:33 ` Alan
2006-11-24 14:10   ` Martin A. Fink
2006-11-24 14:30     ` Alan
2006-11-24 14:54       ` Martin A. Fink
2006-11-25 19:23     ` Andrew Morton [this message]
2006-11-24 14:05 ` Ed Sweetman
2006-11-24 22:10 ` J.A. Magallón
2006-11-24 14:30 Daniel J Blueman
2006-11-28 10:09 Martin A. Fink
2006-11-28 10:43 ` Alan

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=20061125112321.1767a53c.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=fink@mpe.mpg.de \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®