[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <495E64D8.1030200@tmr.com>
Date: Fri, 02 Jan 2009 14:02:48 -0500
From: Bill Davidsen <davidsen@....com>
To: linux-kernel@...r.kernel.org
Cc: Ingo Molnar <mingo@...e.hu>,
Jaswinder Singh Rajput <jaswinderlinux@...il.com>,
Valdis.Kletnieks@...edu, Bryan Donlan <bdonlan@...il.com>,
Ingo Brueckl <ib@...peronline.de>,
linux-kernel@...r.kernel.org, "H. Peter Anvin" <hpa@...or.com>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: Replace CONFIG_EMBEDDED [Was: x86 (Linux Tiny): configure out
support for some processor]
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@....com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists