From: tmhikaru@gmail.com
To: Florian Mickler <florian@mickler.org>,
linux-kernel@vger.kernel.org, Greg KH <gregkh@suse.de>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Chase Douglas <chase.douglas@canonical.com>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: PROBLEM: Unusually high load average when idle in 2.6.35, 2.6.35.1 and later
Date: Sat, 2 Oct 2010 23:02:54 -0400 [thread overview]
Message-ID: <20101003030254.GA4901@roll> (raw)
In-Reply-To: <20101001094814.GA5029@roll>
[-- Attachment #1: Type: text/plain, Size: 1245 bytes --]
These final tests I think conclusively prove that I've been on a
wild goose chase. The load average statistic is indeed broken somehow, and I
did bisect it down to where the problem began, however there seems to be no
performance problem related to it I can find. Somehow I must have made a
mistake I didn't catch when I did the original build that led me to believe
on top of the statistic being broken, that it was causing a performance
problem.
All of the make allnoconfig test results finish within a second of
eachother, with four different kernels tested. I think if there really was a
performance problem it would have reared its head sometime during the
multiple compile tests on different kernels I took. I apologize for wasting
everyones time, especially my own :)
Anyway, the results:
2.6.35.6:
make mrproper && XZ_OPT="" CCACHE_DISABLE="1" time make allnoconfig
5.46user 0.51system 0:07.08elapsed 84%CPU (0avgtext+0avgdata 95888maxresident)k
0inputs+1920outputs (0major+126585minor)pagefaults 0swaps
2.6.35:
make mrproper && XZ_OPT="" CCACHE_DISABLE="1" time make allnoconfig
5.42user 0.50system 0:06.24elapsed 95%CPU (0avgtext+0avgdata 95888maxresident)k
0inputs+1920outputs (0major+126585minor)pagefaults 0swaps
Tim McGrath
[-- Attachment #2: Type: application/pgp-signature, Size: 482 bytes --]
next prev parent reply other threads:[~2010-10-03 3:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-01 3:53 PROBLEM: Unusually high load average when idle in 2.6.35, 2.6.35.1 and later tmhikaru
2010-10-01 9:48 ` tmhikaru
2010-10-03 3:02 ` tmhikaru [this message]
2010-10-03 8:41 ` Peter Zijlstra
2010-10-03 10:12 ` Florian Mickler
2010-10-03 12:04 ` Peter Zijlstra
2010-10-03 17:18 ` tmhikaru
2010-10-11 1:09 ` tmhikaru
2010-10-03 10:21 ` Florian Mickler
2010-10-03 17:10 ` tmhikaru
2010-10-01 18:09 ` Greg KH
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=20101003030254.GA4901@roll \
--to=tmhikaru@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=chase.douglas@canonical.com \
--cc=florian@mickler.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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).