Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758111Ab2JaQ3t (ORCPT ); Wed, 31 Oct 2012 12:29:49 -0400 Received: from zene.cmpxchg.org ([85.214.230.12]:33267 "EHLO zene.cmpxchg.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750931Ab2JaQ3s (ORCPT ); Wed, 31 Oct 2012 12:29:48 -0400 Date: Wed, 31 Oct 2012 12:29:33 -0400 From: Johannes Weiner To: Michal Hocko Cc: linux-mm@kvack.org, cgroups@vger.kernel.org, linux-kernel@vger.kernel.org, Andrew Morton , Tejun Heo , Li Zefan , KAMEZAWA Hiroyuki , Balbir Singh , Glauber Costa Subject: Re: [PATCH v3 1/6] memcg: split mem_cgroup_force_empty into reclaiming and reparenting parts Message-ID: <20121031162933.GB2305@cmpxchg.org> References: <1351251453-6140-1-git-send-email-mhocko@suse.cz> <1351251453-6140-2-git-send-email-mhocko@suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1351251453-6140-2-git-send-email-mhocko@suse.cz> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1088 Lines: 23 On Fri, Oct 26, 2012 at 01:37:28PM +0200, Michal Hocko wrote: > mem_cgroup_force_empty did two separate things depending on free_all > parameter from the very beginning. It either reclaimed as many pages as > possible and moved the rest to the parent or just moved charges to the > parent. The first variant is used as memory.force_empty callback while > the later is used from the mem_cgroup_pre_destroy. > > The whole games around gotos are far from being nice and there is no > reason to keep those two functions inside one. Let's split them and > also move the responsibility for css reference counting to their callers > to make to code easier. > > This patch doesn't have any functional changes. > > Signed-off-by: Michal Hocko > Reviewed-by: Tejun Heo Acked-by: Johannes Weiner -- 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/