From: Mel Gorman <mel@csn.ul.ie>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Yohan <kernel@yohan.staff.proxad.net>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: VM issue causing high CPU loads
Date: Wed, 26 Aug 2009 12:08:09 +0100 [thread overview]
Message-ID: <20090826110809.GG10955@csn.ul.ie> (raw)
In-Reply-To: <20090824162155.ce323f08.akpm@linux-foundation.org>
On Mon, Aug 24, 2009 at 04:21:55PM -0700, Andrew Morton wrote:
> On Mon, 24 Aug 2009 16:23:22 +0200
> Yohan <kernel@yohan.staff.proxad.net> wrote:
>
> > Hi,
> >
> > Is someone have an idea for that :
> >
> > http://bugzilla.kernel.org/show_bug.cgi?id=14024
> >
>
> Please generate a kernel profile to work out where all the CPU tie is
> being spent. Documentation/basic_profiling.txt is a starting point.
>
In the absense of a profile, here is a total stab in the dark. Is this a
NUMA machine? If so, is /proc/sys/vm/zone_reclaim_mode set to 1 and does
setting it to 0 help?
This is based on a relatively recent bug where malloc() could stall for
long times with large amounts of CPU usage due to useless scanning in
page reclaim.
--
Mel Gorman
Part-time Phd Student Linux Technology Center
University of Limerick IBM Dublin Software Lab
next prev parent reply other threads:[~2009-08-26 11:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-24 14:23 VM issue causing high CPU loads Yohan
2009-08-24 23:21 ` Andrew Morton
2009-08-26 11:08 ` Mel Gorman [this message]
2009-08-26 11:55 ` Yohan
2009-08-26 11:53 ` Yohan
2009-08-27 8:39 ` Yohan
2009-08-31 20:39 ` Yohan
2009-09-03 0:06 ` Andrew Morton
2009-09-03 13:01 ` Trond Myklebust
2009-09-03 13:39 ` Yohan
2009-09-03 14:02 ` Trond Myklebust
2009-09-03 14:08 ` Yohan
2009-09-03 14:35 ` sunrpc: dynamically allocate credcache hashtables [was: Re: VM issue causing high CPU loads] Miquel van Smoorenburg
2009-09-03 20:05 ` VM issue causing high CPU loads Simon Kirby
2009-09-03 20:49 ` Trond Myklebust
2009-09-03 22:22 ` Simon Kirby
2009-09-04 12:31 ` Trond Myklebust
2009-09-03 21:21 ` Muntz, Daniel
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=20090826110809.GG10955@csn.ul.ie \
--to=mel@csn.ul.ie \
--cc=akpm@linux-foundation.org \
--cc=kernel@yohan.staff.proxad.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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