Re: [PATCH 3/3] memcg: use __this_cpu_sub to decrement stats

2013-10-27 Thread Tejun Heo
On Sun, Oct 27, 2013 at 12:44:36AM -0700, Greg Thelen wrote: > As of v3.11-9444-g3ea67d0 "memcg: add per cgroup writeback pages > accounting" memcg counter errors are possible when moving charged > memory to a different memcg. Charge movement occurs when processing > writes to memory.force_empty,

[PATCH 3/3] memcg: use __this_cpu_sub to decrement stats

2013-10-27 Thread Greg Thelen
As of v3.11-9444-g3ea67d0 "memcg: add per cgroup writeback pages accounting" memcg counter errors are possible when moving charged memory to a different memcg. Charge movement occurs when processing writes to memory.force_empty, moving tasks to a memcg with memcg.move_charge_at_immigrate=1, or

[PATCH 3/3] memcg: use __this_cpu_sub to decrement stats

2013-10-27 Thread Greg Thelen
As of v3.11-9444-g3ea67d0 memcg: add per cgroup writeback pages accounting memcg counter errors are possible when moving charged memory to a different memcg. Charge movement occurs when processing writes to memory.force_empty, moving tasks to a memcg with memcg.move_charge_at_immigrate=1, or

Re: [PATCH 3/3] memcg: use __this_cpu_sub to decrement stats

2013-10-27 Thread Tejun Heo
On Sun, Oct 27, 2013 at 12:44:36AM -0700, Greg Thelen wrote: As of v3.11-9444-g3ea67d0 memcg: add per cgroup writeback pages accounting memcg counter errors are possible when moving charged memory to a different memcg. Charge movement occurs when processing writes to memory.force_empty,