From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932173Ab1EWRBq (ORCPT ); Mon, 23 May 2011 13:01:46 -0400 Received: from mx3.mail.elte.hu ([157.181.1.138]:42955 "EHLO mx3.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932123Ab1EWRBp (ORCPT ); Mon, 23 May 2011 13:01:45 -0400 Date: Mon, 23 May 2011 19:01:26 +0200 From: Ingo Molnar To: Linus Torvalds Cc: Stephen Rothwell , Thomas Gleixner , "H. Peter Anvin" , David Miller , linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, x86@kernel.org, Peter Zijlstra , Andrew Morton Subject: Re: [bloat] Measuring header file bloat effects on kernel build performance: a more than 2x slowdown ... Message-ID: <20110523170126.GA14407@elte.hu> References: <20110520161210.81bbef3a.sfr@canb.auug.org.au> <20110523090918.GA5474@elte.hu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-08-17) X-ELTE-SpamScore: -2.0 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-2.0 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.3.1 -2.0 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Linus Torvalds wrote: > On Mon, May 23, 2011 at 2:09 AM, Ingo Molnar wrote: > > > > I've attached a totally hacky patch that removes all the big #include's from > > kernel/pid.c and includes all structure and API definitions explicitly. > > Hmm. > > A less hacky patch might be to split up "sched.h" into multiple > smaller things and at least get *part* of the way. > Yeah, absolutely - Peter already raised that a couple of days ago in a sched.h discussion so it's on the radar. The hacky patch was really just a throw-away attempt to see where we stand - we only had vague impressions about the level of problems we have, now we know some numbers. > A lot of things want "struct task_struct" (and in some cases thread_info, but > that's already split). > > Much fewer care about the signal stuff. > > And many things probably don't even need the task_struct definition, and > might be perfectly happy with just function calls rather than having intimate > knowledge of the structure layout and an inline function. Yeah. Thanks, Ingo