public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: Rob Landley <landley@trommello.org>
Cc: Bill Davidsen <davidsen@tmr.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: CONFIG_TINY
Date: Tue, 5 Nov 2002 19:05:03 -0700	[thread overview]
Message-ID: <20021106020503.GG13102@opus.bloom.county> (raw)
In-Reply-To: <200211051755.56586.landley@trommello.org>

On Tue, Nov 05, 2002 at 05:55:56PM +0000, Rob Landley wrote:
> On Tuesday 05 November 2002 19:56, Tom Rini wrote:
> > On Tue, Nov 05, 2002 at 02:26:08PM -0500, Bill Davidsen wrote:
> > > On Mon, 4 Nov 2002, Tom Rini wrote:
> > > > On Mon, Nov 04, 2002 at 02:13:48AM +0000, Rob Landley wrote:
> > > > > I've used -Os.  I've compiled dozens and dozens of packages with -Os.
> > > > >  It has always saved at least a few bytes, I have yet to see it make
> > > > > something larger.  And in the benchmarks I've done, the smaller code
> > > > > actually runs slightly faster.  More of it fits in cache, you know.
> > > >
> > > > Then we don't we always use -Os?
> >
> > [snip 6 good reasons]

Okay, let's just call it 5 then...

> 
> Reasons 1 and 2 were that you can't be sure it works on all compiler versions 
> and all platforms until you'e tried it, which you could say about anything.

Not every kernel person wants to, knows how to, or should have to debug
the compiler as well.

> Reason 3, 5, and 6 were about performance gains, when the point of CONFIG_TINY 
> is, in fact, size.

CONFIG_TINY is in fact about asking questions which should reduce the
size, and allowing the user to determine space / speed tradeoffs.

> > So why do we want to force it on for CONFIG_TINY?
> 
> 1) The point of CONFIG_TINY is size?

The point of CONFIG_TINY, as in the current patches is to offer a bunch
of tunables.  From what I read of the patch, nothing actually uses
CONFIG_TINY, except for config.in bits.  Therefore the point of
CONFIG_TINY is not about size, it's about asking questions.  So ask
another question.

> The setting in question is a default value.  CONFIG_TINY sets a lot of 
> defaults at once, and gives you something grep for if you don't like them.  I 
> realise this isn't what you want, but objecting to patches because they're 
> completely unrelated to what you want is kind of silly.

CONFIG_TINY sets no default values right now.  Go look at
http://www.jaquet.dk/kernel/config_tiny/2.5.44-allinone and tell me
where CONFIG_TINY sets defaults.

Anyhow, I hope to have enough time to finish up a rough cut of my
template work this week and post something for comments.  I've just got
to figure out how to get TWEAK_XXX to work in the Makefiles like
CONFIG_XXX does now.

-- 
Tom Rini (TR1265)
http://gate.crashing.org/~trini/

  reply	other threads:[~2002-11-06  1:58 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-30 22:36 CONFIG_TINY Rasmus Andersen
2002-10-30 23:48 ` CONFIG_TINY Rik van Riel
2002-10-31  0:53 ` CONFIG_TINY Adrian Bunk
2002-10-31  1:10   ` CONFIG_TINY Tom Rini
2002-10-31  5:33     ` CONFIG_TINY Mark Mielke
2002-10-31 14:33       ` CONFIG_TINY Tom Rini
2002-10-31 16:51         ` CONFIG_TINY Mark Mielke
2002-10-31 17:04           ` CONFIG_TINY Tom Rini
2002-10-31 17:12             ` CONFIG_TINY Mark Mielke
2002-10-31 17:24               ` CONFIG_TINY Tom Rini
2002-10-31 17:49                 ` CONFIG_TINY Sam Ravnborg
2002-10-31 18:11                   ` CONFIG_TINY Tom Rini
2002-11-01  2:09                 ` CONFIG_TINY Bill Davidsen
2002-11-01 14:12                   ` CONFIG_TINY Tom Rini
2002-10-31 18:26             ` CONFIG_TINY Kent Borg
2002-10-31 18:53               ` CONFIG_TINY Tom Rini
2002-11-04  2:13                 ` CONFIG_TINY Rob Landley
2002-11-04 19:50                   ` CONFIG_TINY Tom Rini
2002-11-04 20:34                     ` CONFIG_TINY Cort Dougan
2002-11-04 16:16                       ` CONFIG_TINY Rob Landley
2002-11-04 22:30                         ` CONFIG_TINY Eli Carter
2002-11-01  2:10             ` CONFIG_TINY Arnaldo Carvalho de Melo
2002-10-31 21:12           ` CONFIG_TINY Luc Van Oostenryck
2002-10-31 17:08         ` CONFIG_TINY Matt Porter
2002-10-31 16:52           ` CONFIG_TINY Bernd Petrovitsch
2002-10-31 18:43             ` CONFIG_TINY Rasmus Andersen
2002-10-31 19:15               ` CONFIG_TINY Tom Rini
2002-10-31 19:27                 ` CONFIG_TINY Rasmus Andersen
2002-11-01 14:19                   ` CONFIG_TINY Tom Rini
2002-10-31 23:30               ` CONFIG_TINY Bernd Petrovitsch
2002-11-01  6:17                 ` CONFIG_TINY Rasmus Andersen
2002-11-01 22:05                   ` CONFIG_TINY Bernd Petrovitsch
2002-11-01 22:10                     ` CONFIG_TINY Rasmus Andersen
2002-11-01  2:03     ` CONFIG_TINY Bill Davidsen
2002-11-01 14:15       ` CONFIG_TINY Tom Rini
2002-11-04  2:13         ` CONFIG_TINY Rob Landley
2002-11-04 19:51           ` CONFIG_TINY Tom Rini
2002-11-04 16:09             ` CONFIG_TINY Rob Landley
2002-11-05 19:26             ` CONFIG_TINY Bill Davidsen
2002-11-05 19:56               ` CONFIG_TINY Tom Rini
2002-11-05 17:55                 ` CONFIG_TINY Rob Landley
2002-11-06  2:05                   ` Tom Rini [this message]
2002-11-06 14:35                   ` CONFIG_TINY Bill Davidsen
2002-11-05 19:59               ` CONFIG_TINY Alan Cox
2002-10-31  8:24   ` CONFIG_TINY Rasmus Andersen
2002-10-31 10:05     ` CONFIG_TINY Erik Andersen
2002-10-31 10:08       ` CONFIG_TINY Rasmus Andersen
2002-10-31 11:08         ` CONFIG_TINY Erik Andersen
2002-10-31 19:33     ` CONFIG_TINY Daniel Egger
2002-10-31 19:55       ` CONFIG_TINY Rasmus Andersen
2002-10-31  8:32 ` CONFIG_TINY Jens Axboe
2002-10-31  8:53   ` CONFIG_TINY Rasmus Andersen

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=20021106020503.GG13102@opus.bloom.county \
    --to=trini@kernel.crashing.org \
    --cc=davidsen@tmr.com \
    --cc=landley@trommello.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