From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Tue, 13 Dec 2005 10:09:41 +0100 From: Ingo Molnar Subject: Re: [PATCH 1/19] MUTEX: Introduce simple mutex implementation Message-ID: <20051213090941.GA20490@elte.hu> References: <20051212161944.3185a3f9.akpm@osdl.org> <20051213075441.GB6765@elte.hu> <20051213075835.GZ15804@wotan.suse.de> <20051213004257.0f87d814.akpm@osdl.org> <20051213084926.GN23384@wotan.suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051213084926.GN23384@wotan.suse.de> To: Andi Kleen Cc: Andrew Morton , dhowells@redhat.com, torvalds@osdl.org, hch@infradead.org, arjan@infradead.org, matthew@wil.cx, linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org List-ID: * Andi Kleen wrote: > > It's time to give up on it and just drink more coffee or play more tetris > > or something, I'm afraid. > > Or start using icecream (http://wiki.kde.org/icecream) distcc is pretty good too. I have a minimal kernel build done in 19 seconds, a fuller build (1.5MB bzImage that boots on all my testboxes) done in 45 seconds, using gcc 4.0.2. with the default settings, distcc wasnt saturating my boxes, the key was to start distccd with a longer queue size (/etc/sysconfig/distccd): OPTIONS="--nice 5 --jobs 128" and to get the DISTCC_HOSTS tuning right: export DISTCC_HOSTS='j/16 n/120 v/40 s/13 e2/7' in fact my distcc builds are almost as fast as a fully cached ccache build coming straight out of RAM ... Ingo