linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: "linux-mm@kvack.org" <linux-mm@kvack.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"nishimura@mxp.nes.nec.co.jp" <nishimura@mxp.nes.nec.co.jp>,
	"balbir@linux.vnet.ibm.com" <balbir@linux.vnet.ibm.com>,
	kirill@shutemov.name
Subject: [RFC][PATCH 0/3] memcg: oom notifier at el. (v3)
Date: Thu, 11 Mar 2010 16:53:15 +0900	[thread overview]
Message-ID: <20100311165315.c282d6d2.kamezawa.hiroyu@jp.fujitsu.com> (raw)

Updated against mmotm-Mar9.

This patch set's feature is
 - add filter to memcg's oom waitq.
 - oom kill notifier for memcg.
 - oom kill disable for memcg.

Major changes since previous one are
 - add filter to wakeup queue.
 - use its own function and logic rather than reusing thresholds.
 - some minor fixes.

If oom-killer disabled, all tasks under memcg will sleep in memcg_oom_waitq.
What users can do when memcg-oom-killer is disabled is:
 - enlarge limit.
 - kill some task. ---(*)
 - move some task to other cgroup. (with account migration)
   (This patchset doesn't handle a case when account migraion isn't set.)

The benefit of (*) is that the user can save information of all tasks before
killing and he can take coredump (by gcore.) of troublesome process.

I'm now wondering when I remove RFC...but I think this will not have
much HUNK with dirty_ratio sets.

If some codes are unclear, feel free to request me.

Thanks,
-Kame

--
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:[~2010-03-11  7:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-11  7:53 KAMEZAWA Hiroyuki [this message]
2010-03-11  7:55 ` [RFC][PATCH 1/3] memcg: wake up filter in oom waitqueue KAMEZAWA Hiroyuki
2010-03-12  2:30   ` Daisuke Nishimura
2010-03-12  2:38     ` KAMEZAWA Hiroyuki
2010-03-12  2:54       ` Daisuke Nishimura
2010-03-12  3:03         ` KAMEZAWA Hiroyuki
2010-03-11  7:57 ` [RFC][PATCH 2/3] memcg: oom notifier KAMEZAWA Hiroyuki
2010-03-11 14:47   ` Kirill A. Shutemov
2010-03-11 23:54     ` KAMEZAWA Hiroyuki
2010-03-11  7:58 ` [RFC][PATCH 3/3] memcg: oom kill disable and stop and go hooks KAMEZAWA Hiroyuki

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=20100311165315.c282d6d2.kamezawa.hiroyu@jp.fujitsu.com \
    --to=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=kirill@shutemov.name \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=nishimura@mxp.nes.nec.co.jp \
    /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