From: Andi Kleen <ak@linux•intel.com>
To: Michal Marek <mmarek@suse•cz>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: Re: linux-next: clean up the kbuild tree?
Date: Fri, 20 Nov 2015 17:00:33 -0800 [thread overview]
Message-ID: <20151121010033.GB8438@tassilo.jf.intel.com> (raw)
In-Reply-To: <5649D3B9.7020701@suse.cz>
Sorry for the delay.
On Mon, Nov 16, 2015 at 02:01:45PM +0100, Michal Marek wrote:
> Dne 15.11.2015 v 18:58 Andi Kleen napsal(a):
> > On Sun, Nov 15, 2015 at 11:27:05AM +1100, Stephen Rothwell wrote:
> >> Hi Michal,
> >>
> >> I notice that the kbuild tree (relative to Linus' tree) only contains
> >> lots of merges and these 2 commits from April 2014:
> >
> > Really should get in that patch officially. I have a variety of users.
> > And it clearly has been tested long enough in linux-next :)
> > Michal, enough to just repost it?
>
> So the commit in kbuild.git tree is identical to what is being tested
> out of tree? Could you nevertheless provide an updated changelog? One
Yes. I'll provide a new ChangeLog.
> (and actually only) of Linus' objections was that it was not clear at
> all what the actual benefits for the kernel itself are. Do you have some
> benchmarks perhaps, where LTO achieves a preformance gain?
The main users use it to shrink the kernel. I'll run some new benchmarks.
> Also, did the
> compile time impact change with gcc 5.x?
5.x is better than 4.x but it's still a slower. It's also not incremential.
-Andi
--
ak@linux•intel.com -- Speaking for myself only
next prev parent reply other threads:[~2015-11-21 1:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-15 0:27 linux-next: clean up the kbuild tree? Stephen Rothwell
2015-11-15 17:58 ` Andi Kleen
2015-11-16 13:01 ` Michal Marek
2015-11-21 1:00 ` Andi Kleen [this message]
2015-11-21 10:55 ` Takashi Iwai
2015-11-24 2:12 ` Andi Kleen
2015-11-24 16:33 ` LTO build errors (Re: linux-next: clean up the kbuild tree?) Takashi Iwai
2015-11-25 4:33 ` Andi Kleen
2015-11-25 6:58 ` Takashi Iwai
2015-11-30 17:46 ` 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=20151121010033.GB8438@tassilo.jf.intel.com \
--to=ak@linux$(echo .)intel.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mmarek@suse$(echo .)cz \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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