From: Michal Hocko <mhocko@kernel.org>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: linux-mm@kvack.org, akpm@linux-foundation.org,
torvalds@linux-foundation.org, mgorman@suse.de,
rientjes@google.com, riel@redhat.com, hughd@google.com,
oleg@redhat.com, andrea@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH -v2] mm, oom: introduce oom reaper
Date: Tue, 1 Dec 2015 14:29:28 +0100 [thread overview]
Message-ID: <20151201132927.GG4567@dhcp22.suse.cz> (raw)
In-Reply-To: <201511290110.FJB87096.OHJLVQOSFFtMFO@I-love.SAKURA.ne.jp>
On Sun 29-11-15 01:10:10, Tetsuo Handa wrote:
> Tetsuo Handa wrote:
> > > Users of mmap_sem which need it for write should be carefully reviewed
> > > to use _killable waiting as much as possible and reduce allocations
> > > requests done with the lock held to absolute minimum to reduce the risk
> > > even further.
> >
> > It will be nice if we can have down_write_killable()/down_read_killable().
>
> It will be nice if we can also have __GFP_KILLABLE.
Well, we already do this implicitly because OOM killer will
automatically do mark_oom_victim if it has fatal_signal_pending and then
__alloc_pages_slowpath fails the allocation if the memory reserves do
not help to finish the allocation.
> Although currently it can't
> be perfect because reclaim functions called from __alloc_pages_slowpath() use
> unkillable waits, starting from just bail out as with __GFP_NORETRY when
> fatal_signal_pending(current) is true will be helpful.
>
> So far I'm hitting no problem with testers except the one using mmap()/munmap().
>
> I think that cmpxchg() was not needed.
It is not needed right now but I would rather not depend on the oom
mutex here. This is not a hot path where an atomic would add an
overhead.
> diff --git a/mm/oom_kill.c b/mm/oom_kill.c
> index c2ab7f9..1a65739 100644
> --- a/mm/oom_kill.c
> +++ b/mm/oom_kill.c
> @@ -483,8 +483,6 @@ static int oom_reaper(void *unused)
>
> static void wake_oom_reaper(struct mm_struct *mm)
> {
> - struct mm_struct *old_mm;
> -
> if (!oom_reaper_th)
> return;
>
> @@ -492,14 +490,15 @@ static void wake_oom_reaper(struct mm_struct *mm)
> * Make sure that only a single mm is ever queued for the reaper
> * because multiple are not necessary and the operation might be
> * disruptive so better reduce it to the bare minimum.
> + * Caller is serialized by oom_lock mutex.
> */
> - old_mm = cmpxchg(&mm_to_reap, NULL, mm);
> - if (!old_mm) {
> + if (!mm_to_reap) {
> /*
> * Pin the given mm. Use mm_count instead of mm_users because
> * we do not want to delay the address space tear down.
> */
> atomic_inc(&mm->mm_count);
> + mm_to_reap = mm;
> wake_up(&oom_reaper_wait);
> }
> }
--
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-12-01 13:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 15:56 [RFC PATCH] " Michal Hocko
2015-11-25 20:08 ` Johannes Weiner
2015-11-26 11:08 ` Michal Hocko
2015-11-26 15:24 ` Tetsuo Handa
2015-11-26 16:34 ` Michal Hocko
2015-11-26 17:31 ` Michal Hocko
2015-11-27 11:29 ` Tetsuo Handa
2015-11-27 12:35 ` Michal Hocko
2015-11-27 16:12 ` [RFC PATCH -v2] " Michal Hocko
2015-11-27 16:39 ` Mel Gorman
2015-12-01 13:07 ` Michal Hocko
2015-11-28 4:39 ` Tetsuo Handa
2015-11-28 16:10 ` Tetsuo Handa
2015-12-01 13:29 ` Michal Hocko [this message]
2015-12-05 12:33 ` Tetsuo Handa
2015-12-07 16:07 ` Michal Hocko
2015-12-07 22:19 ` Tetsuo Handa
2015-12-08 11:06 ` Michal Hocko
2015-12-01 13:22 ` Michal Hocko
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=20151201132927.GG4567@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=andrea@kernel.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=oleg@redhat.com \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=riel@redhat.com \
--cc=rientjes@google.com \
--cc=torvalds@linux-foundation.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