> We would never try to propose such a change, and never have.
> Name a scalability change that's hurt the performance of UP by 5%.
> There isn't one.
This is *exactly* the reasoning that every OS marketing weenie has used
for the last 20 years to justify their "feature" of the week.
The road to slow bloated code is paved one cache miss at a time. You
may quote me on that. In fact, print it out and put it above your
monitor and look at it every day. One cache miss at a time. How much
does one cache miss add to any benchmark? .001%? Less.
But your pet features didn't slow the system down. Nope, they just made
the cache smaller, which you didn't notice because whatever artificial
benchmark you ran didn't happen to need the whole cache.
You need to understand that system resources belong to the user. Not the
kernel. The goal is to have all of the kernel code running under any
load be less than 1% of the CPU. Your 5% number up there would pretty
much double the amount of time we spend in the kernel for most workloads.
-- --- Larry McVoy lm at bitmover.com http://www.bitmover.com/lm - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Feb 23 2003 - 22:00:37 EST