linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@kernel.org>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: rientjes@google.com, hannes@cmpxchg.org, linux-mm@kvack.org
Subject: Re: [PATCH] mm, oom: Disable preemption during OOM-kill operation.
Date: Wed, 23 Sep 2015 22:23:11 +0200	[thread overview]
Message-ID: <20150923202311.GA19054@dhcp22.suse.cz> (raw)
In-Reply-To: <201509232326.JEB43777.SOFMJOVOLFFtQH@I-love.SAKURA.ne.jp>

On Wed 23-09-15 23:26:35, Tetsuo Handa wrote:
[...]
> Sprinkling preempt_{enable,disable} all around the oom path can temporarily
> slow down threads with higher priority. But doing so can guarantee that
> the oom path is not delayed indefinitely. Imagine a scenario where a task
> with idle priority called the oom path and other tasks with normal or
> realtime priority preempt. How long will we hold oom_lock and keep the
> system under oom?

What I've tried to say is that the OOM killer context might get priority
boost to make sure it makes sufficient progress. This would be much more
systematic approach IMO than sprinkling preempt_{enable,disable} all over
the place.
-- 
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>

  reply	other threads:[~2015-09-23 20:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-19  7:05 Tetsuo Handa
2015-09-22 16:55 ` Michal Hocko
2015-09-23 14:26   ` Tetsuo Handa
2015-09-23 20:23     ` Michal Hocko [this message]
2015-09-27  5:51       ` Tetsuo Handa

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=20150923202311.GA19054@dhcp22.suse.cz \
    --to=mhocko@kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=linux-mm@kvack.org \
    --cc=penguin-kernel@I-love.SAKURA.ne.jp \
    --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