From: Ingo Molnar <mingo@elte.hu>
To: "Sanders, Rob M." <sanders-rob@zai.com>
Cc: Ray Lee <ray-lk@madrabbit.org>,
linux-kernel@vger.kernel.org, bart.vanassche@gmail.com
Subject: Re: Performance changes between 2.6.13 and 2.6.23
Date: Fri, 28 Mar 2008 10:28:56 +0100 [thread overview]
Message-ID: <20080328092856.GC30863@elte.hu> (raw)
In-Reply-To: <D108F32273D3044F8C7B24328CB7713701A4E1@york.rivers.zai.com>
* Sanders, Rob M. <sanders-rob@zai.com> wrote:
> Sorry to disappear for a few days, I just hadn't had time to do
> anything at home. Finally had some time to run some test, and at this
> point I'm thinking that the problem is not with the kernel. Not quite
> sure where to look next, but I've done the following tests:
>
> YDL4.0.91 with 2.6.13 kernel - normal speed
> YDL6.0 with 2.6.23 kenrel - 4-5x slowdown
> YDL4.1 with 2.6.15 kernel - 4-5x slowdown
> YDL4.0.91 with 2.6.15 kernel - *normal speed* - kernel config pulled from YDL4.1 install
> YDL4.0.91 with 2.6.23 kernel - failed boot
if you suspect the scheduler then please try the following suggestions i
made in another thread:
---------->
could you run this script while such a slowdown is really prominent:
http://people.redhat.com/mingo/cfs-scheduler/tools/cfs-debug-info.sh
and send me the output it generates? The output is the most useful if
you do this on a kernel that has CONFIG_SCHED_DEBUG=y and
CONFIG_SCHEDSTATS=y enabled.
on the off chance that this issue has been fixed in the soon-to-be
2.6.25 kernel, you might also want to try x86.git/latest, which is based
on the latest Linus tree and has all relevant x86 fixes and improvements
added as well:
http://people.redhat.com/mingo/x86.git/README
several of the changes can affect performance.
a third (and most comprehensive) way to debug this would be to send me a
scheduler trace of such a slowdown, you can generate a scheduler trace
the following way:
http://people.redhat.com/mingo/sched-devel.git/readme-tracer.txt
but we can probably give a first estimation based on the cfs-debug-info
output already. Btw., you can combine the scheduler and the x86 git tree
into a temporary unified tree by doing these two commands:
git-checkout -b tmp x86/latest
git-merge sched-devel/latest
(run "make oldconfig" to pick up the new config options.)
Ingo
next prev parent reply other threads:[~2008-03-28 9:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-25 12:34 Performance changes between 2.6.13 and 2.6.23 Sanders, Rob M.
2008-03-25 13:25 ` Bart Van Assche
2008-03-25 13:52 ` Sanders, Rob M.
2008-03-25 14:23 ` Bart Van Assche
2008-03-25 16:41 ` Ray Lee
2008-03-25 16:44 ` Sanders, Rob M.
2008-03-27 19:37 ` Sanders, Rob M.
2008-03-28 9:28 ` Ingo Molnar [this message]
2008-03-28 10:32 ` Sanders, Rob M.
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=20080328092856.GC30863@elte.hu \
--to=mingo@elte.hu \
--cc=bart.vanassche@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ray-lk@madrabbit.org \
--cc=sanders-rob@zai.com \
/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