public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rogério Brito" <rbrito@ime.usp.br>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Steve Snyder <swsnyder@insightbb.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Testing optimize-for-size suitability?
Date: Sun, 16 Jan 2005 18:18:47 -0200	[thread overview]
Message-ID: <20050116201847.GC4009@ime.usp.br> (raw)
In-Reply-To: <1105890403.8734.20.camel@laptopd505.fenrus.org>

On Jan 16 2005, Arjan van de Ven wrote:
> On Sun, 2005-01-16 at 10:40 -0500, Steve Snyder wrote:
> > Is there a benchmark or set of benchmarks that would allow me to test
> > the suitability of the CONFIG_CC_OPTIMIZE_FOR_SIZE kernel config
> > option?
> 
> it also saves 400 kb of memory that can be used by the pagecache now...
> that doesn't show in a microbenchmark but it's a quite sizable gain if
> you remember that a disk seek is 10msec..that is a LOT of cpu cycles..

Since I'm using a Duron 600MHz (the lowest model, AFAIK), I decided to
compile a new kernel with the -Os option. Despite the scary warning on the
help, it seems to be working fine for the first few moments with Debian's
testing gcc (3.3.5).

I haven't noticed any other improvement, but I guess that more memory
available to applications would never hurt (as long as stability is
preserved).

I will also try to compile other applications (like Firefox), since my main
memory is so limited and the small cache of my processor would surely
appreciate it.

Perhaps it is time to give the tiny-linux project a try to see what other
optimizations I can achieve.


Just another data point, Rogério.

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
  Rogério Brito - rbrito@ime.usp.br - http://www.ime.usp.br/~rbrito
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

  reply	other threads:[~2005-01-16 20:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-16 15:40 Testing optimize-for-size suitability? Steve Snyder
2005-01-16 15:46 ` Arjan van de Ven
2005-01-16 20:18   ` Rogério Brito [this message]
2005-01-19  4:17 ` Adrian Bunk
2005-01-19  5:14   ` Willy Tarreau

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=20050116201847.GC4009@ime.usp.br \
    --to=rbrito@ime.usp.br \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=swsnyder@insightbb.com \
    /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