On Tue, 31 Oct 2000, Richard B. Johnson wrote: > However, these techniques are not useful with a kernel that has an > unknown number of tasks that execute 'programs' that are not known to > the kernel at compile-time, such as a desk-top operating system. yep, exactly. It simply optimizes the wrong thing and restricts architectural flexibility. It is very easy to optimize by making a system more specific. (this is fact is a more or less automatic engineering work) The real optimizations are the ones that do not take away from the generic nature of the system. Ingo - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
- Re: 2.2.18Pre Lan Performance Rocks! David Lang
- Re: 2.2.18Pre Lan Performance Rocks! Ingo Molnar
- Re: 2.2.18Pre Lan Performance Rocks! Jeff V. Merkey
- Re: 2.2.18Pre Lan Performance Rocks! Alan Cox
- Re: 2.2.18Pre Lan Performance Rocks! Jeff V. Merkey
- Re: 2.2.18Pre Lan Performance Rocks! Horst von Brand
- Re: 2.2.18Pre Lan Performance Rocks! Richard B. Johnson
- Re: 2.2.18Pre Lan Performance Rocks! Jeff V. Merkey
- Re: 2.2.18Pre Lan Performance Rocks! Ingo Molnar
- Re: 2.2.18Pre Lan Performance Rocks! Jeff V. Merkey
- Re: 2.2.18Pre Lan Performance Rocks! Ingo Molnar
- Re: 2.2.18Pre Lan Performance Rocks! Daniel Phillips
- Re: 2.2.18Pre Lan Performance Rocks! Daniel Phillips
- Re: 2.2.18Pre Lan Performance Rocks! Michael H. Warfield
- Re: 2.2.18Pre Lan Performance Rocks! Ingo Molnar
- Re: 2.2.18Pre Lan Performance Rocks! Jeff V. Merkey
- Re: 2.2.18Pre Lan Performance Rocks! David Woodhouse
- Re: 2.2.18Pre Lan Performance Rocks! Jeff V. Merkey
- Re: 2.2.18Pre Lan Performance Rocks! Roger Larsson
- Re: 2.2.18Pre Lan Performance Rocks! Jeff V. Merkey
- Re: 2.2.18Pre Lan Performance Rocks! Andi Kleen