From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vladimir Davydov Subject: Re: [patch] mm: memcontrol: track move_lock state internally Date: Mon, 5 Jan 2015 18:30:54 +0300 Message-ID: <20150105153054.GA31111@esperanza> References: <1420232327-13316-1-git-send-email-hannes@cmpxchg.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Return-path: Content-Disposition: inline In-Reply-To: <1420232327-13316-1-git-send-email-hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org> Sender: cgroups-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Content-Transfer-Encoding: 7bit To: Johannes Weiner Cc: Andrew Morton , Michal Hocko , linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org, cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org On Fri, Jan 02, 2015 at 03:58:47PM -0500, Johannes Weiner wrote: > The complexity of memcg page stat synchronization is currently leaking > into the callsites, forcing them to keep track of the move_lock state > and the IRQ flags. Simplify the API by tracking it in the memcg. > > Signed-off-by: Johannes Weiner Reviewed-by: Vladimir Davydov