From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755218Ab2AXIll (ORCPT ); Tue, 24 Jan 2012 03:41:41 -0500 Received: from zene.cmpxchg.org ([85.214.230.12]:55455 "EHLO zene.cmpxchg.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753766Ab2AXIlj (ORCPT ); Tue, 24 Jan 2012 03:41:39 -0500 Date: Tue, 24 Jan 2012 09:41:33 +0100 From: Johannes Weiner To: Ying Han Cc: KAMEZAWA Hiroyuki , "linux-mm@kvack.org" , "linux-kernel@vger.kernel.org" , "akpm@linux-foundation.org" , Michal Hocko , Hugh Dickins Subject: Re: [PATCH] memcg: remove unnecessary thp check at page stat accounting Message-ID: <20120124084133.GD1660@cmpxchg.org> References: <20120119161445.b3a8a9d2.kamezawa.hiroyu@jp.fujitsu.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jan 23, 2012 at 12:11:11PM -0800, Ying Han wrote: > On Wed, Jan 18, 2012 at 11:14 PM, KAMEZAWA Hiroyuki > wrote: > > Thank you very much for reviewing previous RFC series. > > This is a patch against memcg-devel and linux-next (can by applied without HUNKs). > > > > == > > > > From 64641b360839b029bb353fbd95f7554cc806ed05 Mon Sep 17 00:00:00 2001 > > From: KAMEZAWA Hiroyuki > > Date: Thu, 12 Jan 2012 16:08:33 +0900 > > Subject: [PATCH] memcg: remove unnecessary thp check in mem_cgroup_update_page_stat() > > > > commit 58b318ecf(memcg-devel) > >    memcg: make mem_cgroup_split_huge_fixup() more efficient > > removes move_lock_page_cgroup() in thp-split path. > > > > So, We do not have to check PageTransHuge in mem_cgroup_update_page_stat > > and fallback into the locked accounting because both move charge and thp > > split up are done with compound_lock so they cannot race. update vs. > > move is protected by the mem_cgroup_stealed sufficiently. > > Sorry, i don't see we changed the "move charge" to "move account" ? move_account() moves charges. IMO, it's the function that is a misnomer and "moving charges" is less ambiguous since we account several different things in the memory controller.