On 05/15/2013 05:36 PM, Dan Magenheimer wrote:
If you disagree with any of my arguments earlier in this thread, please say so. Else, please reinforce that the MM subsystem needs to dynamically adapt to a broad range of workloads, which zswap does not (yet) do. Zswap is not simple, it is simplistic*. IMHO, it may be OK for a driver to be ham-handed in its memory use, but that's not OK for something in mm/.
It is functionality that a lot of people want. IMHO it should be where it has most eyes on it, so its deficiencies can be fixed. At this point all we know is that zswap is somewhat simplistic, but we have no idea yet what its failures modes are in practice. The only way to find out, is to start using it. -- All rights reversed _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
