From: Linus Torvalds <torvalds@linux-foundation.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
David Miller <davem@davemloft.net>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
x86@kernel.org, Peter Zijlstra <a.p.zijlstra@chello.nl>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [bloat] Measuring header file bloat effects on kernel build performance: a more than 2x slowdown ...
Date: Mon, 23 May 2011 09:01:44 -0700 [thread overview]
Message-ID: <BANLkTim_pWfU0=ck8=F1kt_bwjtdGRDgdQ@mail.gmail.com> (raw)
In-Reply-To: <20110523090918.GA5474@elte.hu>
On Mon, May 23, 2011 at 2:09 AM, Ingo Molnar <mingo@elte.hu> 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.
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.
Linus
next prev parent reply other threads:[~2011-05-23 16:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 6:12 linux-next: build failure after merge of the final tree Stephen Rothwell
2011-05-20 15:24 ` Linus Torvalds
2011-05-20 16:16 ` Thomas Gleixner
2011-05-20 16:29 ` Linus Torvalds
2011-05-23 9:09 ` [bloat] Measuring header file bloat effects on kernel build performance: a more than 2x slowdown Ingo Molnar
2011-05-23 10:21 ` Alexey Dobriyan
2011-05-23 10:55 ` Ingo Molnar
2011-05-23 11:13 ` Alexey Dobriyan
2011-05-23 11:51 ` Ingo Molnar
2011-05-23 16:01 ` Linus Torvalds [this message]
2011-05-23 17:01 ` Ingo Molnar
2011-05-23 16:19 ` Sam Ravnborg
2011-05-28 0:36 ` Paul Gortmaker
2011-05-28 14:40 ` [PATCH] Fixes to the module.h splitup tree Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='BANLkTim_pWfU0=ck8=F1kt_bwjtdGRDgdQ@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).