I don't think there's really any point in doing that.
None of the regular VM guys are really working 2.5 at this time.
VM has a close relationship with buffers, so tinkering
with the VM while I'm busily driving a truck through the
buffer layer and setting up new writeback mechanisms
would represent some wasted effort.
We don't know yet whether 2.5 will have a reverse-mapping
VM. If it does, then maintenance work against the current
one is wasted effort and more patching pain.
(I'd also like to investigate the option of not throttling
page allocators by making them wait on I/O - make them
wait on pages coming free instead).
So. My vote would be that unless the VM is actually impeding
developers who are working on other parts of the kernel (it
is not) then just leave it as-is for the while.
-
-
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/