From: Stefan Foerster <stefan@stefan-foerster.de>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Very bad interactivity with 2.6.0 and SCSI disks (aic7xxx)
Date: Tue, 19 Aug 2003 07:43:27 +0200 [thread overview]
Message-ID: <20030819054327.GA8674@in-ws-001.cid-net.de> (raw)
In-Reply-To: <20030817230325.2887ca49.akpm@osdl.org>
[I've sent this mail aleready, but got an error from my MAILER-DAEMON.
Perhaps ist was too large vor lkml, so I'm moving the oprofile output
to a webserver]
* Andrew Morton <akpm@osdl.org> wrote:
> Stefan Foerster <stefan@stefan-foerster.de> wrote:
> > * Andrew Morton <akpm@osdl.org> wrote:
> > > Stefan Foerster <stefan@stefan-foerster.de> wrote:
> > > A kernel profile would be needed to diagnose this. You could use
> > > readprofile, but as it may be an interrupt problem, the NMI-based oprofile
> > > output would be better.
> >
> > Is this procedure documented anywhere?
[every information I needed]
I did the following steps:
opcontrol --setup --vmlinux=/usr/src/linux/vmlinux --event=RETIRED_INSNS:100000:0:1:1
Then I used your shell source:
~/shells/oprofileit dd if=/dev/zero of=test bs=1024 count=1048576
opreport -l /usr/src/linux/vmlinux > /tmp/1
opreport -ld -D /usr/src/linux/vmlinux > /tmp/2
During the dd, again the xmms playing a file from an tmpfs froze and
even screen redrawing was very, very slow.
The output of these commands kan be found at:
http://home.in.tum.de/foerstes/oprofile-1
http://home.in.tum.de/foerstes/oprofile-2
Is this information useful in debugging my problem, or should I go and
try again with readprofile or other tools?
Ciao,
Stefan
next prev parent reply other threads:[~2003-08-19 5:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-18 1:32 Very bad interactivity with 2.6.0 and SCSI disks (aic7xxx) Stefan Foerster
2003-08-18 2:21 ` Andrew Morton
2003-08-18 2:31 ` William Lee Irwin III
2003-08-18 5:48 ` Stefan Foerster
2003-08-18 6:03 ` Andrew Morton
2003-08-19 5:43 ` Stefan Foerster [this message]
2003-08-19 5:54 ` Nick Piggin
2003-08-18 19:04 ` Justin T. Gibbs
2003-08-18 19:49 ` Stefan Foerster
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=20030819054327.GA8674@in-ws-001.cid-net.de \
--to=stefan@stefan-foerster.de \
--cc=akpm@osdl.org \
--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;
as well as URLs for NNTP newsgroup(s).