linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: linux-mm@kvack.org
Cc: akpm@linux-foundation.org, oleg@redhat.com, rientjes@google.com,
	vdavydov@parallels.com, mst@redhat.com, mhocko@suse.com,
	mhocko@kernel.org
Subject: [PATCH v2 0/6] Change OOM killer to use list of mm_struct.
Date: Fri, 8 Jul 2016 00:58:41 +0900	[thread overview]
Message-ID: <201607080058.BFI87504.JtFOOFQFVHSLOM@I-love.SAKURA.ne.jp> (raw)

This series is an update of
http://lkml.kernel.org/r/201607031135.AAH95347.MVOHQtFJFLOOFS@I-love.SAKURA.ne.jp .

This series is based on top of linux-next-20160707 +
http://lkml.kernel.org/r/1467201562-6709-1-git-send-email-mhocko@kernel.org .

 include/linux/mm_types.h |    7 +
 include/linux/oom.h      |   14 --
 include/linux/sched.h    |    2
 kernel/exit.c            |    2
 kernel/fork.c            |    4
 mm/memcontrol.c          |   14 --
 mm/oom_kill.c            |  297 ++++++++++++++++++-----------------------------
 7 files changed, 140 insertions(+), 200 deletions(-)

[PATCH 1/6] mm,oom_reaper: Reduce find_lock_task_mm() usage.
[PATCH 2/6] mm,oom_reaper: Do not attempt to reap a task twice.
[PATCH 3/6] mm,oom: Use list of mm_struct used by OOM victims.
[PATCH 4/6] mm,oom_reaper: Make OOM reaper use list of mm_struct.
[PATCH 5/6] mm,oom: Remove OOM_SCAN_ABORT case and signal_struct->oom_victims.
[PATCH 6/6] mm,oom: Stop clearing TIF_MEMDIE on remote thread.

This series does not include patches for use_mm() users and wait_event()
in oom_killer_disable(). We can apply
http://lkml.kernel.org/r/1467365190-24640-3-git-send-email-mhocko@kernel.org
on top of this series.

--
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:[~2016-07-07 15:58 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-07 15:58 Tetsuo Handa [this message]
2016-07-07 16:00 ` [PATCH 1/6] mm,oom_reaper: Reduce find_lock_task_mm() usage Tetsuo Handa
2016-07-11 12:02   ` Michal Hocko
2016-07-07 16:01 ` [PATCH 2/6] mm,oom_reaper: Do not attempt to reap a task twice Tetsuo Handa
2016-07-11 12:15   ` Michal Hocko
2016-07-07 16:03 ` [PATCH 3/6] mm,oom: Use list of mm_struct used by OOM victims Tetsuo Handa
2016-07-11 12:50   ` Michal Hocko
2016-07-12  6:00     ` Tetsuo Handa
2016-07-12  7:09       ` Michal Hocko
2016-07-07 16:04 ` [PATCH 4/6] mm,oom_reaper: Make OOM reaper use list of mm_struct Tetsuo Handa
2016-07-11 13:16   ` Michal Hocko
2016-07-12 13:38     ` Tetsuo Handa
2016-07-12 13:46       ` Michal Hocko
2016-07-12 13:55         ` Michal Hocko
2016-07-12 14:01           ` Tetsuo Handa
2016-07-07 16:06 ` [PATCH 5/6] mm,oom: Remove OOM_SCAN_ABORT case and signal_struct->oom_victims Tetsuo Handa
2016-07-11 13:19   ` Michal Hocko
2016-07-07 16:07 ` [PATCH 6/6] mm,oom: Stop clearing TIF_MEMDIE on remote thread Tetsuo Handa
2016-07-11 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=201607080058.BFI87504.JtFOOFQFVHSLOM@I-love.SAKURA.ne.jp \
    --to=penguin-kernel@i-love.sakura.ne.jp \
    --cc=akpm@linux-foundation.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@kernel.org \
    --cc=mhocko@suse.com \
    --cc=mst@redhat.com \
    --cc=oleg@redhat.com \
    --cc=rientjes@google.com \
    --cc=vdavydov@parallels.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