public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Timothy Miller <miller@techsource.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Adrian Bunk <bunk@fs.tum.de>, linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] add an -Os config option
Date: Tue, 12 Aug 2003 11:43:50 -0400	[thread overview]
Message-ID: <3F390B36.5050709@techsource.com> (raw)
In-Reply-To: 20030812080634.A19427@infradead.org



Christoph Hellwig wrote:
> On Mon, Aug 11, 2003 at 11:11:45PM +0200, Adrian Bunk wrote:
> 
>>The patch below adds an option OPTIMIZE_FOR_SIZE (depending on EMBEDDED) 
>>that changes the optimization from -O2 to -Os.
> 
> 
> Please dropt the if EMBEDDED - this makes perfecty sense for lots of
> todays hardware..
> 
> In fact we should probably rather do some some benchmarking whether it
> would be a good idea to make -Os the default.


Interesting thought...  In reality, we want the system to spend as 
little time in the kernel as possible.  If we've done that job right, 
then optimizing for size shouldn't matter as much.  We're still spending 
most of our time in user space.

Furthermore, it may be that we could benefit from compiling some source 
files with -Os and others with -O2, depending on how critical they are 
and how much they are ACTUALLY affected.

So... we need profiling to determine what is used and how much.  And we 
need benchmarking to determine what is affected and by how much.  Over 
the next couple of years, it might be good for Linus and others to adopt 
a policy where the default optimization for individual files is 
determined based on experience and need.

If only 5% of the source files are compiled with -O2, that's not going 
to bloat the kernel much, we'll get an optimal balance of performance 
and size, and everyone will be happy.

We may find it valuable to divide up the sources differently.  There may 
be source files with both critical and noncritical functions that needed 
to be separated out so they can be compiled differently.

And while we're at it, if there is ever any benefit to -O3, that could 
be used on a per-file basis as well.

Comments?


  reply	other threads:[~2003-08-12 15:29 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-11 21:11 [2.6 patch] add an -Os config option Adrian Bunk
2003-08-11 21:19 ` Michael Buesch
2003-08-11 21:37   ` Mike Fedyk
2003-08-11 21:39   ` Christophe Saout
2003-08-11 21:41   ` Dagfinn Ilmari Mannsåker
2003-08-12  1:29   ` Gene Heskett
2003-08-12  2:51     ` Thomas Molina
2003-08-12  4:14       ` [OT] " Steven Cole
2003-08-12 15:25         ` Timothy Miller
2003-08-12 14:48       ` Gene Heskett
2003-08-12 10:11     ` Michael Buesch
2003-08-12 14:42       ` Gene Heskett
2003-08-12  1:45   ` Warren Turkal
2003-08-11 22:20 ` Russell King
2003-08-12  7:06 ` Christoph Hellwig
2003-08-12 15:43   ` Timothy Miller [this message]
2003-08-12 15:58     ` Adrian Bunk
2003-08-12 16:03     ` Kevin P. Fleming
2003-08-12 13:35 ` Alan Cox
2003-08-12 15:45   ` Joe Korty
2003-08-12 18:03   ` Timothy Miller
  -- strict thread matches above, loose matches on Subject: below --
2003-08-12 19:43 John Bradford

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=3F390B36.5050709@techsource.com \
    --to=miller@techsource.com \
    --cc=bunk@fs.tum.de \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.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