From: Andi Kleen <ak@suse.de>
To: Tilman Schmidt <tilman@imap.cc>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
jbeulich@novell.com
Subject: Re: [2.6.18-rc7-mm1] slow boot
Date: Thu, 28 Sep 2006 19:12:01 +0200 [thread overview]
Message-ID: <200609281912.01858.ak@suse.de> (raw)
In-Reply-To: <451BFFA9.4030000@imap.cc>
On Thursday 28 September 2006 19:00, Tilman Schmidt wrote:
missing context here, but ...
> On 24.09.2006 23:53, Andrew Morton wrote:
> > Do you have the time to go through the
> > http://www.zip.com.au/~akpm/linux/patches/stuff/bisecting-mm-trees.txt
> > process?
>
> Phew, it's done. And the winner is:
>
> x86_64-mm-i386-stacktrace-unwinder.patch
> --------8<--------8<--------8<--------8<--------8<--------8<--------
> i386: Do stacktracer conversion too
>
> Following x86-64 patches. Reuses code from them in fact.
>
> Convert the standard backtracer to do all output using
> callbacks. Use the x86-64 stack tracer implementation
> that uses these callbacks to implement the stacktrace interface.
>
> This allows to use the new dwarf2 unwinder for stacktrace
> and get better backtraces.
>
> Cc: mingo@elte.hu
>
> Signed-off-by: Andi Kleen <ak@suse.de>
> -------->8-------->8-------->8-------->8-------->8-------->8--------
>
> Backing out just this patch from 2.6.18-mm1 (and resolving conflicts
> manually the obvious way) gets the boot time back to normal (ie. as
> fast as 2.6.18 mainline) on my
> Linux gx110 2.6.18-mm1-noinitrd #2 PREEMPT Thu Sep 28 18:48:32 CEST 2006 i686 i686 i386 GNU/Linux
> machine.
Hmm, i assume you have lockdep on. The new backtracer is of course slower
than the old one and it will slow down lockdep which takes a lot of backtraces.
But it shouldn't be a significant slowdown.
Can you perhaps boot with profile=1 and then send readprofile output after
boot?
-Andi
next prev parent reply other threads:[~2006-09-28 17:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-24 16:59 [2.6.18-rc7-mm1] slow boot Tilman Schmidt
2006-09-24 19:22 ` Valdis.Kletnieks
2006-09-24 22:02 ` Tilman Schmidt
2006-09-24 21:53 ` Andrew Morton
2006-09-24 22:15 ` Tilman Schmidt
2006-09-24 22:36 ` Alan Cox
2006-09-24 22:41 ` Andrew Morton
2006-09-26 23:48 ` Tilman Schmidt
2006-09-27 0:21 ` Andrew Morton
2006-09-28 17:00 ` Tilman Schmidt
2006-09-28 17:12 ` Andi Kleen [this message]
2006-09-28 23:20 ` Tilman Schmidt
2006-09-28 23:30 ` Randy Dunlap
2006-09-29 0:15 ` Tilman Schmidt
2006-09-29 7:10 ` Jan Beulich
2006-09-29 16:12 ` Andi Kleen
2006-09-29 18:39 ` Ingo Molnar
2006-10-04 7:05 ` Jan Beulich
2006-09-29 8:49 ` Andi Kleen
2006-09-24 21:58 ` [2.6.18-mm1] slow boot (was: [2.6.18-rc7-mm1] slow boot) Tilman Schmidt
2006-09-25 12:09 ` [2.6.18-rc7-mm1] slow boot Alexander Gran
2006-10-25 18:14 ` Tilman Schmidt
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=200609281912.01858.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tilman@imap.cc \
/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