From: Michal Hocko <mhocko@kernel.org>
To: David Rientjes <rientjes@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [patch -mm 2/2] mm, oom: remove unnecessary variable
Date: Wed, 15 Jul 2015 11:33:36 +0200 [thread overview]
Message-ID: <20150715093336.GD5101@dhcp22.suse.cz> (raw)
In-Reply-To: <alpine.DEB.2.10.1507141644530.16182@chino.kir.corp.google.com>
On Tue 14-07-15 16:45:13, David Rientjes wrote:
> The "killed" variable in out_of_memory() can be removed since the call to
> oom_kill_process() where we should block to allow the process time to
> exit is obvious.
>
> Signed-off-by: David Rientjes <rientjes@google.com>
Acked-by: Michal Hocko <mhocko@suse.com>
> ---
> mm/oom_kill.c | 21 ++++++++-------------
> 1 file changed, 8 insertions(+), 13 deletions(-)
>
> diff --git a/mm/oom_kill.c b/mm/oom_kill.c
> --- a/mm/oom_kill.c
> +++ b/mm/oom_kill.c
> @@ -645,7 +645,6 @@ bool out_of_memory(struct oom_control *oc)
> unsigned long freed = 0;
> unsigned int uninitialized_var(points);
> enum oom_constraint constraint = CONSTRAINT_NONE;
> - int killed = 0;
>
> if (oom_killer_disabled)
> return false;
> @@ -653,7 +652,7 @@ bool out_of_memory(struct oom_control *oc)
> blocking_notifier_call_chain(&oom_notify_list, 0, &freed);
> if (freed > 0)
> /* Got some memory back in the last second. */
> - goto out;
> + return true;
>
> /*
> * If current has a pending SIGKILL or is exiting, then automatically
> @@ -666,7 +665,7 @@ bool out_of_memory(struct oom_control *oc)
> if (current->mm &&
> (fatal_signal_pending(current) || task_will_free_mem(current))) {
> mark_oom_victim(current);
> - goto out;
> + return true;
> }
>
> /*
> @@ -684,7 +683,7 @@ bool out_of_memory(struct oom_control *oc)
> get_task_struct(current);
> oom_kill_process(oc, current, 0, totalpages, NULL,
> "Out of memory (oom_kill_allocating_task)");
> - goto out;
> + return true;
> }
>
> p = select_bad_process(oc, &points, totalpages);
> @@ -696,16 +695,12 @@ bool out_of_memory(struct oom_control *oc)
> if (p && p != (void *)-1UL) {
> oom_kill_process(oc, p, points, totalpages, NULL,
> "Out of memory");
> - killed = 1;
> - }
> -out:
> - /*
> - * Give the killed threads a good chance of exiting before trying to
> - * allocate memory again.
> - */
> - if (killed)
> + /*
> + * Give the killed process a good chance to exit before trying
> + * to allocate memory again.
> + */
> schedule_timeout_killable(1);
> -
> + }
> return true;
> }
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
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>
prev parent reply other threads:[~2015-07-15 9:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 23:45 [patch -mm 1/2] mm, oom: add description of struct oom_control David Rientjes
2015-07-14 23:45 ` [patch -mm 2/2] mm, oom: remove unnecessary variable David Rientjes
2015-07-15 9:33 ` Michal Hocko [this message]
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=20150715093336.GD5101@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.com \
--cc=sergey.senozhatsky.work@gmail.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