Re: [patch] mm: memcontrol: track move_lock state internally

2015-01-05 Thread Vladimir Davydov
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: J

Re: [patch] mm: memcontrol: track move_lock state internally

2015-01-05 Thread Michal Hocko
On Fri 02-01-15 15:58:47, 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. OK, 16B per memcg is OK considering