linux-kernel - Re: [REGRESSION] Recent change to kernel spikes out ccache/distcc

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: <20090106180414.GB10903@mit.edu>
Date:	Tue, 6 Jan 2009 13:04:14 -0500
From:	Theodore Tso <tytso@....edu>
To:	Sam Ravnborg <sam@...nborg.org>
Cc:	Jan Beulich <jbeulich@...ell.com>, ccache@...ts.samba.org,
	linux-kernel@...r.kernel.org
Subject: Re: [REGRESSION] Recent change to kernel spikes out ccache/distcc

On Tue, Jan 06, 2009 at 06:48:25PM +0100, Sam Ravnborg wrote:
> 
> I'm all ears for inputs how to make them even a little more readable.
> We actually used several iteratiosn of Jan's patch just to improve
> readability in areas the patch touched.
> 
> I think at least half of the unreadability comes from the fact that
> people do not realise the steps needed to actually build the kernel.

Yeah, I thought about that a lot, but I couldn't come up with a
constructive suggestion.  The best I could come up with to have kbuild
generate a shell script helper or use a shell script helper to
actually build each .o file.  However, the speed hit probably makes
that unacceptable, although it would make it easier, I suspect, to use
that abstractionas part of making something which ccache or distcc
could use to cache (or distribute to a cluster) all of the steps
needed to build each object file.  Maybe a helper C program instead?

       	  	     	    	   	   - Ted

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