> I don't agree with this, for a very simple reason.
> The current rmap patch was created in order to change the
> VM behaviour as little as possible and ONLY provide an
> infrastructure. Benchmarking a completely untuned thing
> that was built to not change anything is bound to give
> meaningless results.
> I say we _use_ the infrastructure that akpm is trying to
> get merged now in order to implement something useful.
I do agree with Rik here. Once the basic rmap infrastructure is merged
we need to work on implementing stuff on top of it or else there is no
If we cannot show the infrastructure is useful, then Linus will surely
rip rmap out of the kernel in time.
Summary: once it is in and seems correct we need to start providing (in
_pieces_) parts from Rik's full rmap patch and other VM-related code for
2.5 to see where rmap can take us...
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/