I don't really understand the reasons for all those discussions.
As long as you have a maintainer, why don't you just put swap prefetch into=
=20
the kernel, marked experimental, default deactivated so anyone who just=20
make[s] oldconfig (or defaultconfig) won't get it. If anyone finds a good=20
solution for all those cache 'poisoning' problems and problems concerning=20
swapin on workload changes and such swap prefetch can easily taken out agai=
n=20
and no one has to complain and continuing maintaining it.
Actually the same goes for plugshed (having it might have kept Con as a=20
valuable developer).
I am actually waiting for more than 2 years that reiser4 will make it into =
the=20
kernel (sure, marked experimental or even highly experimental) so the=20
patch-journey for every new kernel comes to an end. And most things in-kern=
el=20
will surely be tested more intense so bugs will come up much faster.=20
(Constantly running MM kernels is not really an option since many things in=
=20
there can't be deactivated if they don't work as expected since lots of=20
patches also concern 'vital' parts of the kernel.)

=2E..just 2cents from a happy CK user for it made it possible to watch a mo=
vie=20
while compiling the system - which was impossible with mainline kernel, eve=
n=20
on dual core 2.2 GHz AMD64 with 4G RAM !

Dirk.