From: Michal Hocko <mhocko@suse.cz>
To: David Rientjes <rientjes@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [patch 2/3] mm, oom: pass an oom order of -1 when triggered by sysrq
Date: Fri, 19 Jun 2015 09:32:02 +0200 [thread overview]
Message-ID: <20150619073202.GD4913@dhcp22.suse.cz> (raw)
In-Reply-To: <alpine.DEB.2.10.1506181556180.13736@chino.kir.corp.google.com>
On Thu 18-06-15 16:00:07, David Rientjes wrote:
> The force_kill member of struct oom_context isn't needed if an order of
> -1 is used instead.
But this doesn't make much sense to me. It is not like we would _have_
to spare few bytes here. The meaning of force_kill is clear while order
with a weird value is a hack. It is harder to follow without any good
reason.
> This patch introduces no functional change.
>
> Signed-off-by: David Rientjes <rientjes@google.com>
> ---
> drivers/tty/sysrq.c | 3 +--
> include/linux/oom.h | 1 -
> mm/memcontrol.c | 1 -
> mm/oom_kill.c | 5 ++---
> mm/page_alloc.c | 1 -
> 5 files changed, 3 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/tty/sysrq.c b/drivers/tty/sysrq.c
> --- a/drivers/tty/sysrq.c
> +++ b/drivers/tty/sysrq.c
> @@ -358,8 +358,7 @@ static void moom_callback(struct work_struct *ignored)
> .zonelist = node_zonelist(first_memory_node, gfp_mask),
> .nodemask = NULL,
> .gfp_mask = gfp_mask,
> - .order = 0,
> - .force_kill = true,
> + .order = -1,
> };
>
> mutex_lock(&oom_lock);
> diff --git a/include/linux/oom.h b/include/linux/oom.h
> --- a/include/linux/oom.h
> +++ b/include/linux/oom.h
> @@ -17,7 +17,6 @@ struct oom_control {
> nodemask_t *nodemask;
> gfp_t gfp_mask;
> int order;
> - bool force_kill;
> };
>
> /*
> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> --- a/mm/memcontrol.c
> +++ b/mm/memcontrol.c
> @@ -1550,7 +1550,6 @@ static void mem_cgroup_out_of_memory(struct mem_cgroup *memcg, gfp_t gfp_mask,
> .nodemask = NULL,
> .gfp_mask = gfp_mask,
> .order = order,
> - .force_kill = false,
> };
> struct mem_cgroup *iter;
> unsigned long chosen_points = 0;
> diff --git a/mm/oom_kill.c b/mm/oom_kill.c
> --- a/mm/oom_kill.c
> +++ b/mm/oom_kill.c
> @@ -265,7 +265,7 @@ enum oom_scan_t oom_scan_process_thread(struct oom_control *oc,
> * Don't allow any other task to have access to the reserves.
> */
> if (test_tsk_thread_flag(task, TIF_MEMDIE)) {
> - if (!oc->force_kill)
> + if (oc->order != -1)
> return OOM_SCAN_ABORT;
> }
> if (!task->mm)
> @@ -278,7 +278,7 @@ enum oom_scan_t oom_scan_process_thread(struct oom_control *oc,
> if (oom_task_origin(task))
> return OOM_SCAN_SELECT;
>
> - if (task_will_free_mem(task) && !oc->force_kill)
> + if (task_will_free_mem(task) && oc->order != -1)
> return OOM_SCAN_ABORT;
>
> return OOM_SCAN_OK;
> @@ -718,7 +718,6 @@ void pagefault_out_of_memory(void)
> .nodemask = NULL,
> .gfp_mask = 0,
> .order = 0,
> - .force_kill = false,
> };
>
> if (mem_cgroup_oom_synchronize(true))
> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> --- a/mm/page_alloc.c
> +++ b/mm/page_alloc.c
> @@ -2685,7 +2685,6 @@ __alloc_pages_may_oom(gfp_t gfp_mask, unsigned int order,
> .nodemask = ac->nodemask,
> .gfp_mask = gfp_mask,
> .order = order,
> - .force_kill = false,
> };
> struct page *page;
>
--
Michal Hocko
SUSE Labs
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2015-06-19 7:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-18 23:00 [patch 1/3] mm, oom: organize oom context into struct David Rientjes
2015-06-18 23:00 ` [patch 2/3] mm, oom: pass an oom order of -1 when triggered by sysrq David Rientjes
2015-06-19 7:32 ` Michal Hocko [this message]
2015-06-30 22:50 ` David Rientjes
2015-06-18 23:00 ` [patch 3/3] mm, oom: do not panic for oom kills triggered from sysrq David Rientjes
2015-06-19 0:14 ` [patch 1/3] mm, oom: organize oom context into struct Sergey Senozhatsky
2015-06-30 22:46 ` David Rientjes
2015-07-01 0:11 ` Sergey Senozhatsky
2015-07-01 21:29 ` David Rientjes
2015-06-19 7:30 ` Michal Hocko
2015-07-01 21:37 ` [patch v2 " David Rientjes
2015-07-01 21:37 ` [patch v2 2/3] " David Rientjes
2015-07-02 6:01 ` Michal Hocko
2015-07-08 23:28 ` David Rientjes
2015-07-01 21:37 ` [patch v2 3/3] " David Rientjes
2015-07-02 6:00 ` [patch v2 1/3] " Michal Hocko
2015-07-08 23:42 ` [patch v3 " David Rientjes
2015-07-08 23:42 ` [patch v3 2/3] mm, oom: pass an oom order of -1 when triggered by sysrq David Rientjes
2015-07-08 23:42 ` [patch v3 3/3] mm, oom: do not panic for oom kills triggered from sysrq David Rientjes
2015-07-14 22:52 ` [patch v3 1/3] mm, oom: organize oom context into struct Andrew Morton
2015-07-14 23:44 ` David Rientjes
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=20150619073202.GD4913@dhcp22.suse.cz \
--to=mhocko@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.com \
/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