All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Andi Kleen <ak@linux.intel.com>, 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:28:02 +0200	[thread overview]
Message-ID: <20140723182802.GV18735@two.firstfloor.org> (raw)
In-Reply-To: <20140723180501.GA15749@ravnborg.org>

> 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.

Thanks. How much smaller is it? 

Just saving disk space is a good thing.

-Andi

-- 
ak@linux.intel.com -- Speaking for myself only.

  reply	other threads:[~2014-07-23 18:28 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
2014-07-23 18:28       ` Andi Kleen [this message]
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=20140723182802.GV18735@two.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=ak@linux.intel.com \
    --cc=dirk@gouders.net \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@suse.cz \
    --cc=sam@ravnborg.org \
    /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.