[Devel] Re: [PATCH 1/2] memcg: dirty pages accounting and limiting infrastructure

David Rientjes rientjes at google.com
Mon Feb 22 13:21:53 PST 2010

On Mon, 22 Feb 2010, Andrea Righi wrote:

> > Hmm...do we need spinlock ? You use "unsigned long", then, read-write
> > is always atomic if not read-modify-write.
> I think I simply copy&paste the memcg->swappiness case. But I agree,
> read-write should be atomic.

We don't need memcg->reclaim_param_lock in get_swappiness() or
Containers mailing list
Containers at lists.linux-foundation.org

More information about the Devel mailing list