From: Shakeel Butt <shakeelb@google.com>
To: Yue Zhao <findns94@gmail.com>
Cc: akpm@linux-foundation.org, roman.gushchin@linux.dev,
hannes@cmpxchg.org, mhocko@kernel.org, muchun.song@linux.dev,
willy@infradead.org, linux-mm@kvack.org,
cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
tangyeechou@gmail.com
Subject: Re: [PATCH v2, 0/4] mm, memcg: cgroup v1 and v2 tunable load/store tearing fixes
Date: Mon, 6 Mar 2023 08:25:57 -0800 [thread overview]
Message-ID: <CALvZod5z4F=mS=kgd4DOy8HHCDpL--hxw2uf_bjE+7Svs5ps_g@mail.gmail.com> (raw)
In-Reply-To: <20230306154138.3775-1-findns94@gmail.com>
On Mon, Mar 6, 2023 at 7:42 AM Yue Zhao <findns94@gmail.com> wrote:
>
> This patch series helps to prevent load/store tearing in
> several cgroup knobs.
>
> As kindly pointed out by Michal Hocko and Roman Gushchin
> , the changelog has been rephrased.
>
> Besides, more knobs were checked, according to kind suggestions
> from Shakeel Butt and Muchun Song.
>
> v1:
> - Add [WRITE|READ]_ONCE for memcg->oom_group
> v2:
> - Rephrase changelog
> - Add [WRITE|READ]_ONCE for memcg->oom_kill_disable,
> memcg->swappiness, vm_swappiness and memcg->soft_limit
>
Thanks Yue and for the whole series:
Acked-by: Shakeel Butt <shakeelb@google.com>
next prev parent reply other threads:[~2023-03-06 16:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 15:41 Yue Zhao
2023-03-06 15:41 ` [PATCH v2, 1/4] mm, memcg: Prevent memory.oom.group load/store tearing Yue Zhao
2023-03-06 17:47 ` Michal Hocko
2023-03-06 15:41 ` [PATCH v2, 2/4] mm, memcg: Prevent memory.swappiness " Yue Zhao
2023-03-06 17:50 ` Michal Hocko
2023-03-06 15:41 ` [PATCH v2, 3/4] mm, memcg: Prevent memory.oom_control " Yue Zhao
2023-03-06 17:53 ` Michal Hocko
2023-03-08 14:51 ` Martin Zhao
2023-03-06 15:41 ` [PATCH v2, 4/4] mm, memcg: Prevent memory.soft_limit_in_bytes " Yue Zhao
2023-03-06 17:55 ` Michal Hocko
2023-03-06 16:25 ` Shakeel Butt [this message]
2023-03-06 17:51 ` [PATCH v2, 0/4] mm, memcg: cgroup v1 and v2 tunable load/store tearing fixes Roman Gushchin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALvZod5z4F=mS=kgd4DOy8HHCDpL--hxw2uf_bjE+7Svs5ps_g@mail.gmail.com' \
--to=shakeelb@google.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=findns94@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=muchun.song@linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=tangyeechou@gmail.com \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox