From: Adrian Bunk <bunk@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Sam Ravnborg <sam@ravnborg.org>,
linux arch <linux-arch@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
David Miller <davem@davemloft.net>
Subject: Re: [PATCH] prepare kconfig inline optimization for all architectures
Date: Sun, 27 Apr 2008 21:41:06 +0300 [thread overview]
Message-ID: <20080427184106.GD2252@cs181133002.pp.htv.fi> (raw)
In-Reply-To: <alpine.LFD.1.10.0804271053300.2896@woody.linux-foundation.org>
On Sun, Apr 27, 2008 at 11:11:27AM -0700, Linus Torvalds wrote:
>
>
> On Sun, 27 Apr 2008, Adrian Bunk wrote:
> >
> > What I want instead:
> > - we continue to force the compiler to always inline with "inline"
> > - we remove the inline's in .c files and make too big functions in
> > headers out-of-line
>
> Sure, I can agree with that as a mostly good goal, but you're still
> ignoring the fact that nobody should really expect the compiler to always
> do a good job at deciding high-level issues.
>
> For example, what's wrong with having "inline" on functions in .c files if
> the author thinks they are small enough? He's likely right. Considering
> past behaviour, he's quite often more right than the compiler.
>...
Ingo's commit in your tree just broke this assumption.
And he justified breaking it with a 2.3% size decrease.
And after
- grep'ing for "inline" through drivers/
- remembering how driver authors use likely/unlikely
- remembering the practically non-existing quality criteria you set
for new drivers [1]
"He's likely right." is likely not right for the average driver author.
You might be smarter than gcc, but most kernel developers (including me)
are not.
> Linus
cu
Adrian
[1] you said you really wanted this driver merged in this state in 2.6.25:
grep -C4 volatile drivers/infiniband/hw/nes/nes_nic.c
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2008-04-27 18:41 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-27 10:51 [PATCH] prepare kconfig inline optimization for all architectures Sam Ravnborg
2008-04-27 11:31 ` Adrian Bunk
2008-04-27 11:56 ` Sam Ravnborg
2008-04-27 12:36 ` Ingo Molnar
2008-04-27 12:49 ` Ingo Molnar
2008-04-27 17:06 ` Linus Torvalds
2008-04-27 17:22 ` Adrian Bunk
2008-04-27 17:32 ` Linus Torvalds
2008-04-27 17:47 ` Adrian Bunk
2008-04-27 18:00 ` Christoph Hellwig
2008-04-27 18:09 ` Sam Ravnborg
2008-04-27 18:14 ` Christoph Hellwig
2008-04-27 18:24 ` Linus Torvalds
2008-04-27 18:32 ` Christoph Hellwig
2008-04-27 19:36 ` Ingo Molnar
2008-04-27 19:49 ` Adrian Bunk
2008-04-27 23:26 ` Arjan van de Ven
2008-04-27 23:36 ` Linus Torvalds
2008-04-27 23:41 ` Ingo Molnar
2008-04-27 18:31 ` Sam Ravnborg
2008-04-27 18:36 ` Christoph Hellwig
2008-04-27 18:11 ` Linus Torvalds
2008-04-27 18:25 ` Christoph Hellwig
2008-04-27 18:30 ` Linus Torvalds
2008-04-27 18:41 ` Adrian Bunk [this message]
2008-04-27 18:57 ` Linus Torvalds
2008-04-27 20:51 ` Mike Galbraith
2008-04-27 17:57 ` Christoph Hellwig
2008-04-27 17:40 ` Matthew Wilcox
2008-04-27 17:59 ` Adrian Bunk
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=20080427184106.GD2252@cs181133002.pp.htv.fi \
--to=bunk@kernel.org \
--cc=davem@davemloft.net \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sam@ravnborg.org \
--cc=torvalds@linux-foundation.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