Re: [PATCH] memcg: first step towards hierarchical controller

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Jun 26, 2012 at 10:22:04PM +0400, Glauber Costa wrote:
> I would agree with you if we were changing a fundamental algorithm,
> with no way to resort back to a default setup. We are not removing any
> functionality whatsoever here.
> 
> I would agree with you if we were actually documenting explicitly
> that this is an expected default behavior.
> 
> But we never made the claim that use_hierarchy would default to 0.
> 
> Well, we seldom make claims about default values of any tunables. We
> just expect them to be reasonable values, and we seem to agree that
> this is, indeed, reasonable.

No, we can't change behavior in this major way silently.  Any change
of this scale must be explicit.  The behavior change is not only major
but also subtle at the same time.  If a user is using flat hierarchy
and then boot a new kernel, the user suddenly gets hierarchical
accounting which may or may not cause noticeable problem immediately
and would be difficult like hell to chase down and diagnose.

I don't mind how global switch is implemented but the flip should be
explicit no matter what.  This is something we simply CAN NOT do.

Thanks.

-- 
tejun

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>


[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]