From: Sam Ravnborg <sam@ravnborg.org>
To: Andi Kleen <ak@linux.intel.com>
Cc: Andi Kleen <andi@firstfloor.org>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
Dirk Gouders <dirk@gouders.net>,
mmarek@suse.cz
Subject: Re: [PATCH 1/2] kbuild: Support split debug info v3
Date: Wed, 23 Jul 2014 20:05:01 +0200 [thread overview]
Message-ID: <20140723180501.GA15749@ravnborg.org> (raw)
In-Reply-To: <20140720211901.GQ5803@tassilo.jf.intel.com>
On Sun, Jul 20, 2014 at 02:19:01PM -0700, Andi Kleen wrote:
> > Why are as only called with -Wa,-gdwarf-2 in the non-split case?
> > Is this a bug or intentional?
> > If it is intentional then it is not explained.
>
> Probably was a merging mistake. Will fix.
>
> > > + help
> > > + Generate debug info into separate .dwo files. This can be
> > > + faster for building than including the debug information directly
> > Here the "faster" part is promoted.
> > But in your cover letter you actually highlight the "smaller" case
> > as more significant.
> > Maybe include info on both positive items.
>
> I currently don't see it significantly faster in my setup, will
> mention size. It may be in others though. Feel free to test.
I tried to test this on my setup - it is a Intel Atom with 2 cores.
16 GB RAM, a 7200 RPM stat disk.
In other words a low-spec setup.
Base config was "make allnoconfig"
make KCFLAGS=-g
real 3m35.967s
user 12m19.270s
sys 1m15.082s
make KCFLAGS=-gsplit-dwarf
real 3m33.366s
user 12m11.156s
sys 1m17.772s
I did like this:
echo time make -j4 -s KCFLAGS=-gsplit-dwarf
time make -j4 -s KCFLAGS=-gsplit-dwarf
echo time make -j4 -s KCFLAGS=-g
time make -j4 -s KCFLAGS=-g
echo time make -j4 -s KCFLAGS=-gsplit-dwarf
time make -j4 -s KCFLAGS=-gsplit-dwarf
echo time make -j4 -s KCFLAGS=-g
time make -j4 -s KCFLAGS=-g
echo time make -j4 -s KCFLAGS=-gsplit-dwarf
time make -j4 -s KCFLAGS=-gsplit-dwarf
echo time make -j4 -s KCFLAGS=-g
time make -j4 -s KCFLAGS=-g
The figures are from last run - but the other runs had compareable times.
So in short I see a ~3 seconds speedup - out of 210 seconds.
Thats less than I anticipated.
But a speed-up never the less - which was consistent over all three runs.
Sam
next prev parent reply other threads:[~2014-07-23 18:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-15 23:16 [PATCH 1/2] kbuild: Support split debug info v3 Andi Kleen
2014-07-15 23:16 ` [PATCH 2/2] Kbuild: Add a option to enable dwarf4 Andi Kleen
2014-07-20 19:23 ` Sam Ravnborg
2014-07-20 21:17 ` Andi Kleen
2014-07-20 19:04 ` [PATCH 1/2] kbuild: Support split debug info v3 Sam Ravnborg
2014-07-20 21:19 ` Andi Kleen
2014-07-23 18:05 ` Sam Ravnborg [this message]
2014-07-23 18:28 ` Andi Kleen
2014-07-24 8:10 ` Dirk Gouders
-- strict thread matches above, loose matches on Subject: below --
2014-05-16 22:06 Andi Kleen
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=20140723180501.GA15749@ravnborg.org \
--to=sam@ravnborg.org \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=dirk@gouders.net \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.