From: Shakeel Butt <shakeelb@google.com>
To: Yafang Shao <laoar.shao@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@kernel.org>, Roman Gushchin <guro@fb.com>,
Greg Thelen <gthelen@google.com>, Linux MM <linux-mm@kvack.org>
Subject: Re: [PATCH 1/2] mm, memcg: better name mem_cgroup_out_of_memory()
Date: Sun, 3 May 2020 15:20:52 -0700 [thread overview]
Message-ID: <CALvZod41y_nHe_oGwrqev58yC8XUVHbJFq2KLZ9g=UyRsWQnjw@mail.gmail.com> (raw)
In-Reply-To: <20200502143452.7640-2-laoar.shao@gmail.com>
On Sat, May 2, 2020 at 7:35 AM Yafang Shao <laoar.shao@gmail.com> wrote:
>
> Rename mem_cgroup_out_of_memory() to mem_cgroup_oom_kill() to indicate
> that this function is used to try to kill a process.
> With this change it will cooperate better with the oom events.
> function memcg event
> mem_cgroup_oom() oom
> mem_cgroup_oom_kill() oom_kill
>
> Cc: Shakeel Butt <shakeelb@google.com>
> Cc: Johannes Weiner <hannes@cmpxchg.org>
> Cc: Michal Hocko <mhocko@kernel.org>
> Cc: Roman Gushchin <guro@fb.com>
> Cc: Greg Thelen <gthelen@google.com>
> Signed-off-by: Yafang Shao <laoar.shao@gmail.com>
Reviewed-by: Shakeel Butt <shakeelb@google.com>
> ---
> mm/memcontrol.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> index 5beea03dd58a..985edce98491 100644
> --- a/mm/memcontrol.c
> +++ b/mm/memcontrol.c
> @@ -1570,7 +1570,7 @@ unsigned long mem_cgroup_size(struct mem_cgroup *memcg)
> return page_counter_read(&memcg->memory);
> }
>
> -static bool mem_cgroup_out_of_memory(struct mem_cgroup *memcg, gfp_t gfp_mask,
> +static bool mem_cgroup_oom_kill(struct mem_cgroup *memcg, gfp_t gfp_mask,
> int order)
> {
> struct oom_control oc = {
> @@ -1799,7 +1799,7 @@ static enum oom_status mem_cgroup_oom(struct mem_cgroup *memcg, gfp_t mask, int
> * relying on the oom victim to make a forward progress and we can
> * invoke the oom killer here.
> *
> - * Please note that mem_cgroup_out_of_memory might fail to find a
> + * Please note that mem_cgroup_oom_kill might fail to find a
> * victim and then we have to bail out from the charge path.
> */
> if (memcg->oom_kill_disable) {
> @@ -1821,7 +1821,7 @@ static enum oom_status mem_cgroup_oom(struct mem_cgroup *memcg, gfp_t mask, int
> mem_cgroup_oom_notify(memcg);
>
> mem_cgroup_unmark_under_oom(memcg);
> - if (mem_cgroup_out_of_memory(memcg, mask, order))
> + if (mem_cgroup_oom_kill(memcg, mask, order))
> ret = OOM_SUCCESS;
> else
> ret = OOM_FAILED;
> @@ -1879,7 +1879,7 @@ bool mem_cgroup_oom_synchronize(bool handle)
> if (locked && !memcg->oom_kill_disable) {
> mem_cgroup_unmark_under_oom(memcg);
> finish_wait(&memcg_oom_waitq, &owait.wait);
> - mem_cgroup_out_of_memory(memcg, current->memcg_oom_gfp_mask,
> + mem_cgroup_oom_kill(memcg, current->memcg_oom_gfp_mask,
> current->memcg_oom_order);
> } else {
> schedule();
> @@ -6102,7 +6102,7 @@ static ssize_t memory_max_write(struct kernfs_open_file *of,
> }
>
> memcg_memory_event(memcg, MEMCG_OOM);
> - if (!mem_cgroup_out_of_memory(memcg, GFP_KERNEL, 0))
> + if (!mem_cgroup_oom_kill(memcg, GFP_KERNEL, 0))
> break;
> }
>
> --
> 2.18.2
>
next prev parent reply other threads:[~2020-05-03 22:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-02 14:34 [PATCH 0/2] memcg oom: don't try to kill a process if there is no process Yafang Shao
2020-05-02 14:34 ` [PATCH 1/2] mm, memcg: better name mem_cgroup_out_of_memory() Yafang Shao
2020-05-03 22:20 ` Shakeel Butt [this message]
2020-05-02 14:34 ` [PATCH 2/2] mm, memcg: don't try to kill a process if memcg is not populated Yafang Shao
2020-05-03 22:59 ` Shakeel Butt
2020-05-04 3:03 ` Yafang Shao
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='CALvZod41y_nHe_oGwrqev58yC8XUVHbJFq2KLZ9g=UyRsWQnjw@mail.gmail.com' \
--to=shakeelb@google.com \
--cc=akpm@linux-foundation.org \
--cc=gthelen@google.com \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=laoar.shao@gmail.com \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.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