public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Gortmaker <p_gortmaker@yahoo.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: marcelo@conectiva.com.br, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] bluesmoke/MCE support optional
Date: Fri, 01 Mar 2002 02:18:37 -0500	[thread overview]
Message-ID: <3C7F2B4D.71CD3C3B@yahoo.com> (raw)
In-Reply-To: <E16gaeU-0001di-00@the-village.bc.nu>

Alan Cox wrote:

> Is the MCE code big enough to justify this ? Last time I checked it was
> 1800 bytes 1000 of which were __init

Granted it isn't a huge monster (yet; size below) so use your own judgement;
I won't be upset either way.  I should note that a well respected developer
recently stated (on l-k) the following about making things unconditional:

	There are those of us trying to stuff Linux into embedded devices 
	who if anything want more configuration options not people taking 
	stuff out.

:-)

Same person went on to suggest:

	What I'd much rather see if this is an issue is:

	bool    'Do you want to customise for a very small system'

	which auto enables all the random small stuff if you say no, and goes
	much deeper into options if you say yes.

...an idea I like, but probably not appropriate for 2.4 - so perhaps I'll
work on a CONFIG_TINY for 2.5 if it is generally accepted as an ok plan.

Paul.
--
			bluesmoke.o:

Idx Name          Size      VMA       LMA       File off  Algn
  0 .text         000001cb  00000000  00000000  00000040  2**4
                  CONTENTS, ALLOC, LOAD, RELOC, READONLY, CODE
  1 .data         00000004  00000000  00000000  0000020c  2**2
                  CONTENTS, ALLOC, LOAD, RELOC, DATA
  2 .bss          00000008  00000000  00000000  00000210  2**2
                  ALLOC
  3 .note         00000014  00000000  00000000  00000210  2**0
                  CONTENTS, READONLY
  4 .data.init    0000000e  00000000  00000000  00000224  2**2
                  CONTENTS, ALLOC, LOAD, DATA
  5 .rodata       000002d7  00000000  00000000  00000240  2**5
                  CONTENTS, ALLOC, LOAD, READONLY, DATA
  6 .text.init    000001cd  00000000  00000000  00000520  2**4
                  CONTENTS, ALLOC, LOAD, RELOC, READONLY, CODE
  7 .setup.init   00000010  00000000  00000000  000006f0  2**2
                  CONTENTS, ALLOC, LOAD, RELOC, DATA
  8 .comment      00000026  00000000  00000000  00000700  2**0
                  CONTENTS, READONLY





  reply	other threads:[~2002-03-01 10:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-28 15:01 [PATCH] bluesmoke/MCE support optional Paul Gortmaker
2002-03-01  0:11 ` Alan Cox
2002-03-01  7:18   ` Paul Gortmaker [this message]
2002-03-01 11:51     ` Alan Cox
2002-03-01  9:56   ` Dave Jones
2002-03-01  2:47 ` Mike Fedyk
2002-03-01 12:31   ` Alan Cox
2002-03-01 12:55     ` Dave Jones
2002-03-03 10:57       ` Paul Gortmaker
2002-03-03 13:53         ` Alan Cox
2002-03-01 15:10     ` Marcelo Tosatti
2002-03-01 17:29       ` Alan Cox

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=3C7F2B4D.71CD3C3B@yahoo.com \
    --to=p_gortmaker@yahoo.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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