From: Minchan Kim <minchan@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>, Michal Hocko <mhocko@suse.com>
Subject: Re: [PATCH] mm: introduce oom_kill_disable sysctl knob
Date: Fri, 6 Nov 2020 14:59:16 -0800 [thread overview]
Message-ID: <20201106225916.GA1383786@google.com> (raw)
In-Reply-To: <57a31f2e-bb08-7303-e5fc-fe00e832cee6@infradead.org>
On Fri, Nov 06, 2020 at 12:46:47PM -0800, Randy Dunlap wrote:
> Hi,
>
> Fix a few typos:
>
> On 11/6/20 12:32 PM, Minchan Kim wrote:
> > ---
> > Documentation/admin-guide/sysctl/vm.rst | 14 ++++++++++++++
> > include/linux/mm.h | 2 ++
> > include/linux/oom.h | 1 +
> > kernel/sysctl.c | 9 +++++++++
> > mm/oom_kill.c | 24 ++++++++++++++++++++++++
> > 5 files changed, 50 insertions(+)
> >
> > diff --git a/Documentation/admin-guide/sysctl/vm.rst b/Documentation/admin-guide/sysctl/vm.rst
> > index f455fa00c00f..49dcedfaf0c0 100644
> > --- a/Documentation/admin-guide/sysctl/vm.rst
> > +++ b/Documentation/admin-guide/sysctl/vm.rst
> > @@ -694,6 +694,20 @@ is used in oom_kill_allocating_task.
> >
> > The default value is 0.
> >
> > +oom_kill_disable
> > +================
> > +
> > +This disables or enables OOM killing in out-of-memory situations.
> > +
> > +If this is set to one, the OOM killer is disabled so OOM kill never
> > +hapens in out-of-memory situation. It could cause system dangerous
>
> happens It could cause a dangerous system
>
> > +state due to memory allocation failure so user should be careful to
>
> careful when
> > +use it.
>
> using it.
>
> > +
> > +If this is set to zero, the OOM killer is enabled so OOM kill happens
> > +in out-of-memory situations.
> > +
> > +The default value is 0.
> >
> > overcommit_kbytes
> > =================
>
> > diff --git a/mm/oom_kill.c b/mm/oom_kill.c
> > index 8b84661a6410..0f48cdeeb1e7 100644
> > --- a/mm/oom_kill.c
> > +++ b/mm/oom_kill.c
>
> > #ifdef CONFIG_NUMA
> > /**
> > * oom_cpuset_eligible() - check task eligiblity for kill
>
> eligibility
>
> but that's not in your patch, so don't bother with it. :)
Sure, I will resend it with fixing after waiting some feedback.
Thanks for the review, Randy.
next prev parent reply other threads:[~2020-11-06 22:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-06 20:32 [PATCH] mm: introduce oom_kill_disable sysctl knob Minchan Kim
2020-11-06 20:46 ` Randy Dunlap
2020-11-06 22:59 ` Minchan Kim [this message]
2020-11-09 7:37 ` Michal Hocko
2020-11-09 15:39 ` Minchan Kim
2020-11-09 16:06 ` Michal Hocko
2020-11-09 16:27 ` Minchan Kim
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=20201106225916.GA1383786@google.com \
--to=minchan@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=rdunlap@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.