[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YQjv+DzdX3CuVfIo@dhcp22.suse.cz>
Date: Tue, 3 Aug 2021 09:27:52 +0200
From: Michal Hocko <mhocko@...e.com>
To: Roman Gushchin <guro@...com>
Cc: Miaohe Lin <linmiaohe@...wei.com>,
"hannes@...xchg.org" <hannes@...xchg.org>,
"vdavydov.dev@...il.com" <vdavydov.dev@...il.com>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"shakeelb@...gle.com" <shakeelb@...gle.com>,
"willy@...radead.org" <willy@...radead.org>,
"alexs@...nel.org" <alexs@...nel.org>,
"richard.weiyang@...il.com" <richard.weiyang@...il.com>,
"songmuchun@...edance.com" <songmuchun@...edance.com>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"cgroups@...r.kernel.org" <cgroups@...r.kernel.org>
Subject: Re: [PATCH 2/5] mm, memcg: narrow the scope of percpu_charge_mutex
On Tue 03-08-21 07:13:35, Roman Gushchin wrote:
> I’d go with atomic_dec().
which is not implying memory barriers either. You would need
atomic_dec_return or some other explicit barrier IIRC.
--
Michal Hocko
SUSE Labs
Powered by blists - more mailing lists