These are two patches to reduce the overhead of memcg, particularly when it's not used. The first is a simple reordering of when a barrier is applied which memcg happens to get burned by. I doubt it is controversial at all. The second optionally disables memcg by default. This should have been the default from the start and it matches what Debian already does today. The difficulty is that existing installations may break if the new kernel parameter is not applied so distributions need to be careful with upgrades. The difference it makes is marginal and only visible in profiles, not headline performance. It'd be understandable if memcg maintainers rejected it but I'll leave it up to them. Documentation/kernel-parameters.txt | 4 ++++ init/Kconfig | 15 +++++++++++++++ kernel/cgroup.c | 20 ++++++++++++++++---- mm/memcontrol.c | 3 +++ mm/memory.c | 10 ++++++---- 5 files changed, 44 insertions(+), 8 deletions(-) -- 2.3.5 -- To unsubscribe from this list: send the line "unsubscribe cgroups" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
