From: Sam Ravnborg <sam@ravnborg.org>
To: Adrian Bunk <bunk@kernel.org>
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [2.6 patch] kernel/sched*: optimize inlining
Date: Sun, 11 May 2008 19:52:22 +0200 [thread overview]
Message-ID: <20080511175222.GA31729@uranus.ravnborg.org> (raw)
In-Reply-To: <20080511092132.GE1645@cs181133002.pp.htv.fi>
On Sun, May 11, 2008 at 12:21:32PM +0300, Adrian Bunk wrote:
> kernel/sched* contained tons of inline's, and the result of removing
> them all is impressing (with x86_64_defconfig)
> text data bss dec hex filename
> 39557 8234 280 48071 bbc7 kernel/sched.o
> 41792 8234 280 50306 c482 kernel/sched.o.old
>
> That's a 5.3% text size reduction (!), which is more than twice as much
> as the 2.3% the "optimized inlining" achieves on average for the whole
> kernel.
If we compare the size of sched.o in the three cases we see a clear effect:
text data bss dec hex filename
forced inline: 31257 2702 200 34159 856f kernel/sched.o
inline hint: 31105 2702 200 34007 84d7 kernel/sched.o
no inline (hint): 30704 2702 200 33606 8346 kernel/sched.o
The last line "no inline(hint)" is with Adrians patch applied.
So what is obvious from the above is that with the arch/gcc combination
I use here the inline hint has a clear effect and gcc inlines more
when we have given it a hint to do so than without the hint.
I conclude this solely on the cide size change between the line
"inline hint" and "no inline(hint)".
With adrians patch there were no difference in size with or
without the OPTIMIZE_INLINING enabled.
Or in other words the config option "OPTIMIZE_INLINING" is NOT
equal to removing all the inline annotations.
>
> Note that any remarks regarding whether this patch might affect the
> performance are invalid since noone cared about the performance when
> the "x86: add optimized inlining" commit that does the same for the
> whole kernel entered the tree.
In one case it was an option it was easy to turn off/on so we could
compare and modulus bugs it was a noop on gcc < 4.0.
With the patch below we revet back to the broken gcc inline algorithm on
gcc < 4.0 and it cannot as easy be turned of (have to revert this patch).
Both issues are worth to consider before applying this.
Sam
next prev parent reply other threads:[~2008-05-11 17:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-11 9:21 [2.6 patch] kernel/sched*: optimize inlining Adrian Bunk
2008-05-11 11:18 ` Andreas Mohr
2008-05-11 12:52 ` Adrian Bunk
2008-05-11 17:22 ` Ray Lee
2008-05-11 17:52 ` Sam Ravnborg [this message]
2008-05-11 18:49 ` Adrian Bunk
2008-05-11 19:42 ` Sam Ravnborg
2008-05-11 20:00 ` Adrian Bunk
2008-05-11 20:38 ` Sam Ravnborg
2008-05-11 21:19 ` Adrian Bunk
2008-05-11 21:44 ` Sam Ravnborg
2008-05-11 22:11 ` Adrian Bunk
2008-05-12 6:57 ` Sam Ravnborg
2008-05-12 7:45 ` Adrian Bunk
[not found] <fa.kBy7Kr77qTR+lDVDv4OKx7n5m1Y@ifi.uio.no>
[not found] ` <fa.8/KGOoB8CQ+uVBJXmUNHaIfXQSg@ifi.uio.no>
[not found] ` <fa.sBJgAJSNbPht40KbEGBXczzW3vQ@ifi.uio.no>
2008-05-11 17:25 ` Robert Hancock
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=20080511175222.GA31729@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.