Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753181AbbETMuw (ORCPT ); Wed, 20 May 2015 08:50:52 -0400 Received: from cantor2.suse.de ([195.135.220.15]:45821 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752268AbbETMut (ORCPT ); Wed, 20 May 2015 08:50:49 -0400 From: Mel Gorman To: Michal Hocko , Johannes Weiner , Andrew Morton Cc: Tejun Heo , Linux-CGroups , Linux-MM , LKML , Mel Gorman Subject: [PATCH 0/2] Reduce overhead of memcg when unused Date: Wed, 20 May 2015 13:50:43 +0100 Message-Id: <1432126245-10908-1-git-send-email-mgorman@suse.de> X-Mailer: git-send-email 2.3.5 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1275 Lines: 27 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 linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/