From: Andrew Morton <akpm@osdl.org>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: sonny@burdell.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: Memory pressure handling with iSCSI
Date: Tue, 26 Jul 2005 14:21:24 -0700 [thread overview]
Message-ID: <20050726142124.44aa0176.akpm@osdl.org> (raw)
In-Reply-To: <1122410256.6433.43.camel@dyn9047017102.beaverton.ibm.com>
Badari Pulavarty <pbadari@us.ibm.com> wrote:
>
> > You probably covered this, but just to make sure, if you're on a
> > pentium4 machine, I usually boot w/ "idle=poll" to see proper idle
> > reporting because otherwise the chip will throttle itself back and
> > idle time will be skewed -- at least on oprofile.
> >
>
> My machine is AMD64.
I'd expect the problem to which Sonny refers will occur on many
architectures.
IIRC, the problem is that many (or all) of the counters which oprofile uses
are turned off when the CPU does a halt. So the profiler ends up thinking
that zero time is spent in the idle handler. The net effect is that if
your workload spends 90% of its time idle then all the other profiler hits
are exaggerated by a factor of ten. Making the CPU busywait in idle()
fixes this.
But you're using the old /proc/profile profiler which uses a free-running
timer which doesn't get stopped by halt, so it is unaffected by this.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2005-07-26 21:21 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-26 17:35 Badari Pulavarty
2005-07-26 18:04 ` Roland Dreier
2005-07-26 18:11 ` Andrew Morton
2005-07-26 18:39 ` Badari Pulavarty
2005-07-26 18:48 ` Andrew Morton
2005-07-26 19:12 ` Andrew Morton
2005-07-26 20:36 ` Badari Pulavarty
2005-07-26 21:11 ` Badari Pulavarty
2005-07-26 21:24 ` Andrew Morton
2005-07-26 21:45 ` Badari Pulavarty
2005-07-26 22:10 ` Andrew Morton
2005-07-26 22:48 ` Badari Pulavarty
2005-07-26 23:07 ` Andrew Morton
2005-07-26 23:26 ` Badari Pulavarty
2005-07-27 0:31 ` Andrew Morton
2005-07-27 1:20 ` Martin J. Bligh
2005-07-27 1:26 ` Andrew Morton
2005-07-27 1:47 ` Martin J. Bligh
2005-07-27 1:31 ` Badari Pulavarty
2005-07-27 1:40 ` Andrew Morton
2005-07-26 19:31 ` Sonny Rao
2005-07-26 20:37 ` Badari Pulavarty
2005-07-26 21:21 ` Andrew Morton [this message]
2005-07-26 20:59 ` Rik van Riel
2005-07-26 21:05 ` Badari Pulavarty
2005-07-26 21:33 ` Martin J. Bligh
2005-07-26 22:05 ` Adam Litke
2005-07-26 21:12 ` Andrew Morton
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=20050726142124.44aa0176.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pbadari@us.ibm.com \
--cc=sonny@burdell.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