Re: raid5d, page_launder and scheduling latency

[Alan Cox]

> Happily, we've just fixed the four most gross sources of poor
> interactivity in the kernel, so let's knock over some of the others as
> well - a few /proc functions.  That mainly leaves zap_page_range() and
> exit() with a lot of open files.

Nowhere near it. We have to fix copy_*_user and strlen_user (there are reasons
2.2 uses strnlen_user). Map the same page into 2Gig of address space filled with
non zero bytes. Map a zero terminator on the end of it. Pass pointers to this
for all your args and do an exec().

Alan