lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110728191824.GB17308@elte.hu>
Date:	Thu, 28 Jul 2011 21:18:24 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Paul Gortmaker <paul.gortmaker@...driver.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
	linux-arch@...r.kernel.org
Subject: Re: [RFC/PULL 00/11] introduce export.h; reduce module.h usage


* Paul Gortmaker <paul.gortmaker@...driver.com> wrote:

> >  - how much does this actually improve compile times (for a 
> > "normal" build or a "allmodconfig" one)?
> 
> Let me run some "real world" use cases and get back to you in a 
> couple of hours with that.  But Ingo's testing on a much earlier 
> snapshot was showing roughly a couple percent.  ( 
> https://lkml.org/lkml/2011/5/28/60 )

I found that it's pretty hard to measure these things accurately and 
reliably, kernel build times are very noisy.

Note that you can use my numbers to estimate expected savings: just 
build before/after .i files in a common directory like kernel/*.c and 
measure their combined size. The size decrease of the preprocessor 
output scales almost linearly with runtime.

You could standardize on that kind of metric "these patches decrease 
preprocessor output by 0.5%" - those translate almost 1:1 into 
compile time speedups, and you don't really have to re-measure 
compile times every time you come up with such patches.

Thanks,

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ