From: Steven Rostedt <rostedt@goodmis.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: "Frédéric Weisbecker" <fweisbec@gmail.com>,
linux-kernel@vger.kernel.org,
"Thomas Gleixner" <tglx@linutronix.de>
Subject: Re: [performance problem] CONFIG_DYNAMIC_FTRACE: Increased kernel build times
Date: Fri, 23 Oct 2009 09:18:51 -0400 [thread overview]
Message-ID: <1256303931.20866.826.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <20091023074533.GA10067@elte.hu>
On Fri, 2009-10-23 at 09:45 +0200, Ingo Molnar wrote:
> Steve,
>
> i did an 64-bit allyesconfig build test (with debug_info disabled), with
> and without CONFIG_DYNAMIC_FTRACE set.
>
> The build time results are:
>
> -CONFIG_DYNAMIC_FTRACE: 266.30
> +CONFIG_DYNAMIC_FTRACE: 296.07 (+11.2%)
>
> So we get more than 10% build time overhead.
>
> That's quite high - higher than what i remember having measured
> originally when the first iteration of the mcount code went in.
>
> This extra overhead comes from the mcount post-processing script
> (scripts/recordmcount.pl) that runs objcopy as well and is written in
> Perl. I think this whole angle needs to be improved - 10% is way too
> high of a price to pay.
Yeah, I know this is quite a hit, and to fix this is on my todo list.
What I plan on doing is checking if libelf is installed, and if it is,
then doing a C program that does the linking and checking. If not, it
defaults back to the perl code.
But I'm bug hunting right now, and that takes a higher priority.
-- Steve
prev parent reply other threads:[~2009-10-23 13:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-23 7:45 Ingo Molnar
[not found] ` <520f0cf10910230307k91d0c80sa3d69bcd74d6e1f1@mail.gmail.com>
2009-10-23 10:18 ` John Kacur
2009-10-23 10:37 ` Ingo Molnar
2009-10-23 13:18 ` Steven Rostedt [this message]
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=1256303931.20866.826.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®