public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>,
	Jaswinder Singh Rajput <jaswinderlinux@gmail.com>,
	Valdis.Kletnieks@vt.edu, Bryan Donlan <bdonlan@gmail.com>,
	Ingo Brueckl <ib@wupperonline.de>,
	linux-kernel@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Replace CONFIG_EMBEDDED [Was: x86 (Linux Tiny): configure out support for some processor]
Date: Fri, 02 Jan 2009 14:02:48 -0500	[thread overview]
Message-ID: <495E64D8.1030200@tmr.com> (raw)
In-Reply-To: <20090102181345.GB5905@uranus.ravnborg.org>

Sam Ravnborg wrote:
>> It's a subjective category and no amount of talking will bring any 
>> solution here.
> 
> It is brought up now and then partly because the use of the
> term EMBEDDED that is so overloaded that it is not fun.
> 
> Someone should kill it and replace it with something saner.
> 
> CONFIG_EXPERT_TEXT_SIZE
> 
> For stuff that the expert can toy with which mainly
> has text size impact and some documented performance/functionality impact.
> The possibility to select a subset of CPU's may belong here.
> 
> 
> CONFIG_EXPERT_DATA_SIZE
> 
> Likewise where what we save is more data than TEXT.
> For example where we lower the size of a hash bucket etc.
> 
> CONFIG_EXPERT
> 
> For other stuff that no 'ordinary' user will need to change
> but the expert may find it usefull.
> 
> Everything we hide under EMBEDDED today would fit in the
> categories above.
> 
> 
Don't forget "CONFIG_EXPERT_STACK_SIZE" for 4k x86 stacks.

-- 
Bill Davidsen <davidsen@tmr.com>
   "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot


  reply	other threads:[~2009-01-02 19:03 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-01 20:37 x86 (Linux Tiny): configure out support for some processors Ingo Brueckl
2009-01-02  5:19 ` Bryan Donlan
2009-01-02  5:59   ` Jaswinder Singh Rajput
2009-01-02  9:38     ` Ingo Molnar
2009-01-02 15:10       ` Jaswinder Singh Rajput
2009-01-02 15:39         ` Valdis.Kletnieks
2009-01-02 16:13           ` Jaswinder Singh Rajput
2009-01-02 16:20             ` Valdis.Kletnieks
2009-01-02 16:23               ` Ingo Molnar
2009-01-02 16:21             ` Ingo Molnar
2009-01-02 16:38               ` Jaswinder Singh Rajput
2009-01-02 17:34                 ` Ingo Molnar
2009-01-02 18:13                   ` Replace CONFIG_EMBEDDED [Was: x86 (Linux Tiny): configure out support for some processor] Sam Ravnborg
2009-01-02 19:02                     ` Bill Davidsen [this message]
2009-01-02 19:31                       ` Sam Ravnborg
2009-01-02 16:51           ` x86 (Linux Tiny): configure out support for some processors david
2009-01-02 16:26             ` Valdis.Kletnieks
2009-01-02 18:54               ` david

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=495E64D8.1030200@tmr.com \
    --to=davidsen@tmr.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=bdonlan@gmail.com \
    --cc=hpa@zytor.com \
    --cc=ib@wupperonline.de \
    --cc=jaswinderlinux@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    /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