From: Yohan <kernel@yohan.staff.proxad.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: VM issue causing high CPU loads
Date: Wed, 26 Aug 2009 13:53:58 +0200 [thread overview]
Message-ID: <4A952256.2030602@yohan.staff.proxad.net> (raw)
In-Reply-To: <20090824162155.ce323f08.akpm@linux-foundation.org>
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.
I did & post the profiles on the bugtrack
I dit it with a 2.6.31-rc7-git2 kernel
(need at least 2 week days after a reboot/drop_cache to really show the
bug)
Thanks
next prev parent reply other threads:[~2009-08-26 11:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4A92A25A.4050608@yohan.staff.proxad.net>
2009-08-24 23:21 ` Andrew Morton
2009-08-26 11:08 ` Mel Gorman
2009-08-26 11:55 ` Yohan
2009-08-26 11:53 ` Yohan [this message]
2009-08-27 8:39 ` Yohan
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=4A952256.2030602@yohan.staff.proxad.net \
--to=kernel@yohan.staff.proxad.net \
--cc=akpm@linux-foundation.org \
--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