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: <20071015181953.GA23130@uranus.ravnborg.org>
Date:	Mon, 15 Oct 2007 20:19:53 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	Philippe Elie <phil.el@...adoo.fr>
Cc:	Rik van Riel <riel@...riel.com>, linux-kernel@...r.kernel.org
Subject: Re: WANTED: kernel projects for CS students

On Mon, Oct 15, 2007 at 06:31:54PM +0200, Philippe Elie wrote:
> > Increase speed for a build with no updates
> > ==========================================
> > On a resonably fast machine with a decent config it takes
> > roughly 10 seconds to do a make where nothing is updated.
> > Generating one single Makefile is assumed to speed up things
> > and will in addition allow a simpler syntax as what is used today
> > for some of the uglier constructs.
> > 
> > Contact: Sam Ravnborg <sam@...nborg.org>
> > Difficulty: 5
> > Language: Perl or C
> 
> Isn't make -j 2 or more implemented by running multiple make in sub-dirs ?
> Parallel make is more and more used even on cheap hardware.

The kernel build system supports parallel make and I guess all
kernel developers use it. People tell me that a 32 way machine is
quite good for kernel compilation.

The bottleneck is that we spawn so many make instances and each have
to read all the same makefiles and stat in total a zillion files
for a simple kernel build.

With a single Makefile we can run a single instance make where
we read all files only once and stat the same file only once.

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