Cc: Willy Tarreau <w@...>, Mark Lord <lkml@...>, Adrian Bunk <bunk@...>, Alan Cox <alan@...>, Shawn Bohrer <shawn.bohrer@...>, Ingo Molnar <mingo@...>, Andrew Morton <akpm@...>, Linux Kernel Mailing List <linux-kernel@...>, Arjan van de Ven <arjan@...>, Thomas Gleixner <tglx@...>
On Sun, 20 April 2008 16:19:29 +0200, Andi Kleen wrote:
It is not uncommon for embedded systems to be designed around 16MiB.
Some may even have less, although I haven't encountered any of those
lately.
When dealing in those dimensions, savings of 100k are substantial. In
some causes they may be the difference between 16MiB or 32MiB, which
translates to manufacturing costs. In others it simply means that the
system can cache a bit more and run faster, or it can have a little more
functionality.
In most cases it simply allows userspace programmers to avoid looking
harder to save those 100k, as they are already saved in kernel space.
Therefore we made life hard for us in order to make life easier for
someone else, saving them time and money.
Whether that is worth it depends on your personal point of view. Many
embedded people will claim "Hell yes!" Of those that don't, most are
simply ignoring currently mainline kernels and will regret the
development later. They care, thay just don't tend to care enough to
engage in these discussions or even know about them. :(
Jörn
--
Eighty percent of success is showing up.
-- Woody Allen
--
