Hello, Glauber.

On Wed, Sep 26, 2012 at 10:36 AM, Glauber Costa [off-list ref] wrote:

This was discussed multiple times. Our interest is to preserve existing
deployed setup, that were tuned in a world where kmem didn't exist.
Because we also feed kmem to the user counter, this may very well
disrupt their setup.

So, that can be served by .kmem_accounted at root, no?

User memory, unlike kernel memory, may very well be totally in control
of the userspace application, so it is not unreasonable to believe that
extra pages appearing in a new kernel version may break them.

It is actually a much worse compatibility problem than flipping
hierarchy, in comparison

Again, what's wrong with one switch at the root?

Thanks.

-- 
tejun