linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "KOSAKI Motohiro" <kosaki.motohiro@jp.fujitsu.com>
To: David Rientjes <rientjes@google.com>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	balbir@linux.vnet.ibm.com,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"menage@google.com" <menage@google.com>,
	Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [discuss][memcg] oom-kill extension
Date: Wed, 29 Oct 2008 15:55:06 +0900	[thread overview]
Message-ID: <2f11576a0810282355t7a5b5cc1id7442229ded104b1@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.10.0810282206260.10159@chino.kir.corp.google.com>

> There was a patchset from February that added /dev/mem_notify to warn
> userspace of low or out of memory conditions:
>
>        http://marc.info/?l=linux-kernel&m=120257050719077
>        http://marc.info/?l=linux-kernel&m=120257050719087
>        http://marc.info/?l=linux-kernel&m=120257062719234
>        http://marc.info/?l=linux-kernel&m=120257071219327
>        http://marc.info/?l=linux-kernel&m=120257071319334
>        http://marc.info/?l=linux-kernel&m=120257080919488
>        http://marc.info/?l=linux-kernel&m=120257081019497
>        http://marc.info/?l=linux-kernel&m=120257096219705
>        http://marc.info/?l=linux-kernel&m=120257096319717
>
> Perhaps this idea can simply be reworked for the memory controller or
> standalone cgroup?

Very sorry.

I know my laziness is wrong.
I have made split-lru effort give priority more than other awhile.

So I'll restart user-land notify effort soon.

Paul, I strongly interest to your implementation.
Could you post your notify patch?

--
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>

  parent reply	other threads:[~2008-10-29  6:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-29  2:38 KAMEZAWA Hiroyuki
2008-10-29  4:08 ` Balbir Singh
2008-10-29  5:00   ` KAMEZAWA Hiroyuki
2008-10-29  5:13     ` David Rientjes
2008-10-29  5:28       ` KAMEZAWA Hiroyuki
2008-10-29  6:55       ` KOSAKI Motohiro [this message]
2008-10-29  5:35 ` Paul Menage
2008-10-29  5:45   ` KAMEZAWA Hiroyuki
2008-10-29  5:49     ` Paul Menage

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=2f11576a0810282355t7a5b5cc1id7442229ded104b1@mail.gmail.com \
    --to=kosaki.motohiro@jp.fujitsu.com \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-mm@kvack.org \
    --cc=menage@google.com \
    --cc=mtosatti@redhat.com \
    --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