From: "Martin J. Bligh" <mbligh@google.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, apw@shadowen.org,
Ingo Molnar <mingo@elte.hu>
Subject: Re: Clear performance regression on reaim7 in 2.6.15-git6
Date: Sat, 15 Apr 2006 15:59:39 -0700 [thread overview]
Message-ID: <44417ADB.4070104@google.com> (raw)
In-Reply-To: <20060415154518.6a5a0c52.akpm@osdl.org>
>>It's still broken in 17-rc1 ... will send you a patch in a sec.
>
>
> I already have kconfigdebug-set-debug_mutex-to-off-by-default.patch queued up.
OK. That explains why -mm2 bounced back at the end of this graph:
http://test.kernel.org/perf/reaim.moe.png
But ... it's still way below what 2.6.15 was. There's another thunk
down between 2.6.16 and 2.6.16-git18, AFAICS.
M.
next prev parent reply other threads:[~2006-04-15 23:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-15 19:10 Clear performance regression on reaim7 in 2.6.15-git6 Martin J. Bligh
2006-04-15 21:17 ` Andrew Morton
2006-04-15 21:31 ` Martin J. Bligh
2006-04-15 21:52 ` Andrew Morton
2006-04-15 22:30 ` Martin J. Bligh
2006-04-15 22:45 ` Andrew Morton
2006-04-15 22:59 ` Martin J. Bligh [this message]
2006-04-15 23:28 ` Martin J. Bligh
2006-04-15 22:56 ` OGAWA Hirofumi
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=44417ADB.4070104@google.com \
--to=mbligh@google.com \
--cc=akpm@osdl.org \
--cc=apw@shadowen.org \
--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