From: Ingo Molnar <mingo@kernel.org>
To: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: Randy Dunlap <rdunlap@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>
Subject: Re: [PATCH/RFC] headers: drop 2 #included headers from <linux/interrupt.h>
Date: Mon, 26 Feb 2018 08:59:31 +0100 [thread overview]
Message-ID: <20180226075931.5vn4vdbfcsje2z56@gmail.com> (raw)
In-Reply-To: <87bmgc3bdv.fsf@rasmusvillemoes.dk>
* Rasmus Villemoes <linux@rasmusvillemoes.dk> wrote:
> [...] Now I finally got around to writing some scripts for that, so here's a
> visualization of (the evolution of) the problem:
>
> https://wildmoose.dk/header-bloat/
Nice! In particular your final conclusion is impressive and scary:
> So the typical (median) translation unit ends up including over 450 headers
> files, making the whole TU about 200 times bigger than the .c file itself, while
> more than 25% of the translation units get bloated to over 400 times the size of
> the .c file.
Even with a lot of this being eliminated at fairly early compiling stages that's a
*huge* chunk of code that needs to be parsed again and again and again and again
...
> I hope to find some time soonish to polish the old programs and see if they
> actually still work.
That would be lovely!
Thanks,
Ingo
next prev parent reply other threads:[~2018-02-26 7:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-16 0:49 [PATCH/RFC] headers: drop 2 #included headers from <linux/interrupt.h> Randy Dunlap
2018-02-16 7:59 ` Ingo Molnar
2018-02-25 23:19 ` Rasmus Villemoes
2018-02-26 7:59 ` Ingo Molnar [this message]
2018-02-16 9:45 ` [tip:core/headers] headers: Drop two " tip-bot for Randy Dunlap
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=20180226075931.5vn4vdbfcsje2z56@gmail.com \
--to=mingo@kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=mingo@redhat.com \
--cc=rdunlap@infradead.org \
--cc=tglx@linutronix.de \
/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