[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BANLkTi=Vbr+DRBy6sa7omGpvAb0uGunYMA@mail.gmail.com>
Date: Mon, 23 May 2011 13:21:22 +0300
From: Alexey Dobriyan <adobriyan@...il.com>
To: Ingo Molnar <mingo@...e.hu>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Thomas Gleixner <tglx@...utronix.de>,
"H. Peter Anvin" <hpa@...or.com>,
David Miller <davem@...emloft.net>, linux-next@...r.kernel.org,
linux-kernel@...r.kernel.org, x86@...nel.org,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [bloat] Measuring header file bloat effects on kernel build
performance: a more than 2x slowdown ...
On Mon, May 23, 2011 at 12:09 PM, Ingo Molnar <mingo@...e.hu> wrote:
> 24594a2bfcaa: [PATCH] x86-64 merge
>
> - Remove some unneeded prefetches. Just two are enough to kickstart
> the hardware prefetcher.
>
> But despite touching prefetches explicitly, this too sloppily left the (now
> dangling) prefetch.h include file around.
Well, developer removes include, developer risks compile breakage.
> Anway, what i tried to demonstrate with this mail how much *real* slowdown in
> the kernel build our current header file bloat is causing. We could literally
> halve our kernel build times if we fixed this!
News at 11!
Ingo, you're running x86 compile tests nonstop, you can very well make asm-x86
headers the strictest ones to make problem less problematic.
You (x86 merge people), removed header guards from quite a lot of asm-x86/*.h
files breaking gcc "do not open(2) second time" heuristics. It became better
since last I've noticed it, but maybe start with that?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists