Re: [2.4.17/18pre] VM and swap - it's really unusable

Is it possible to decide, now what should go into 2.4.18 (maybe -pre3) -aa or 
-rmap?
Andrew Morten`s read-latency.patch is a clear winner for me, too.
What about 00_nanosleep-5 and bootmem?
The O(1) scheduler?
Maybe preemption? It is disengageable so nobody should be harmed but we get 
the chance for wider testing.

Any comments?

Thanks,
	Dieter

-- 
Dieter Nⅳzel
Graduate Student, Computer Science

University of Hamburg
Department of Computer Science
@home: Dieter.Nuetzel _at_ hamburg.de
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo _at_ vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:

Re: [2.4.17/18pre] VM and swap - it's really unusableLuigi Genoni <kernel _at_ Expansa.sns.it>
Re: [2.4.17/18pre] VM and swap - it's really unusable"J.A. Magallon" <jamagallon _at_ able.es>

Prev by Date: Re: PATCH 2.5.2.9: ext2 unbork fs.h (part 1/7)
Next by Date: Re: CBQ ingress problem
Previous by thread: Re: [2.4.17/18pre] VM and swap - it's really unusable
Next by thread: Re: [2.4.17/18pre] VM and swap - it's really unusable
Indexes:[Main][Thread]