From: rwhron@earthlink.net
To: akpm@zip.com.au
Cc: linux-kernel@vger.kernel.org, lse-tech@lists.sourceforge.net
Subject: Re: oprofile results with lmbench
Date: Sat, 13 Jul 2002 16:36:22 -0400 [thread overview]
Message-ID: <20020713203622.GA24297@rushmore> (raw)
> the numbers don't look right.
> Perhaps you fed oprofpp the wrong vmlinux?
Thanks! You are right. I just put a bold message
on the page that the results are invalid. I'm leaving
the page up in case anyone else recommends changes.
I'll re-run the tests.
> btw, when using RETIRED_INSNS (or CPU_CLK_UNHALTED), you should
> boot the kernel with `idle=poll'. Otherwise, idle time is
> unaccounted for in the profile and it gets really hard to interpret,
> and hard to compare runs.
I've added "idle=poll" to my lilo.conf append.
--
Rands Hron
http://home.earthlink.net/~rwhron/kernel/bigbox.html
next reply other threads:[~2002-07-13 20:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-13 20:36 rwhron [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-13 18:57 oprofile results with lmbench rwhron
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=20020713203622.GA24297@rushmore \
--to=rwhron@earthlink.net \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
/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