From: Tim Schmielau <email@example.com>
To: Arnd Bergmann <firstname.lastname@example.org>
Subject: Re: [PATCH] break out task_struct from sched.h
Date: Tue, 1 Oct 2002 00:57:20 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.email@example.com> (raw)
On Mon, 30 Sep 2002, Arnd Bergmann wrote:
> I tried something similar before: I seperated out mm_struct from sched.h
> so that mm.h does not have to include sched.h any more. At that time,
> the results were poor, because most of the files that include mm.h but
> not sched.h actually need 'current' or something else from sched.h
> and I then had to include sched.h by hand in them.
> With your work, it probably makes sense to look into this again.
That'd be great.
> Note that 241 of your 614 files that don't need sched.h still include
> it through either linux/mm.h or linux/interrupt.h, so don't gain anything
Yep, and last time I checked also compile time improvements were poor
(if measurable at all) because of this.
But with further cleanups like what you suggested we'll (slowly, but
I also intend to redo the analysis after further header file detangling,
but let's get this applied first.
prev parent reply other threads:[~2002-09-30 22:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-29 19:50 [PATCH] break out task_struct from sched.h Tim Schmielau
2002-09-29 20:13 ` John Levon
2002-09-29 21:00 ` Tim Schmielau
2002-09-29 21:06 ` Robert Love
2002-09-29 22:17 ` Dave Jones
2002-09-29 22:23 ` Arnaldo Carvalho de Melo
2002-09-30 7:34 ` Tim Schmielau
2002-09-30 12:17 ` Arnd Bergmann
2002-09-30 22:57 ` Tim Schmielau [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).