mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: David Rientjes <rientjes@google.com>
Cc: kosaki.motohiro@jp.fujitsu.com, Rik van Riel <riel@redhat.com>,
	Greg KH <greg@kroah.com>, Arve Hjonnevag <arve@android.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Nick Piggin <npiggin@suse.de>, San Mehat <san@android.com>,
	linux-kernel@vger.kernel.org, Greg KH <gregkh@suse.de>
Subject: Re: [patch 1/5] oom: cleanup android low memory killer
Date: Thu, 14 May 2009 21:23:13 +0900 (JST)	[thread overview]
Message-ID: <20090514211934.F5B3.A69D9226@jp.fujitsu.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0905111241120.23739@chino.kir.corp.google.com>


sorry late responce.

> On Mon, 4 May 2009, Rik van Riel wrote:
> 
> > > There was an interest in a low mem userspace notifier that applications can
> > > poll() on at configurable low mem levels to react accordingly.  This would
> > > probably address the problem that the Android team is trying to fix.
> > 
> > This would also make it easier for virtual machines to be
> > ballooned down to size when the host experiences memory
> > pressure.
> > 
> > The low memory notification could also be useful for JVMs,
> > databases that do (some of) their own caching and any garbage
> > collected program in general.
> > 
> 
> I agree, and I'd suggest that it be implemented as a cgroup so that 
> individual sets of tasks can be responsible for their own lowmem 
> notifiers.
> 
> KOSAKI, you were pushing the /dev/mem_notify patchset last year from 
> Marcelo.  Do you have any plans of recreating that in a cgroup or have you 
> dropped it?

sorry, I've pending this because I think I have to stabilize VM 
as top priority.

I can't say when I resume this works, sorry.




      reply	other threads:[~2009-05-14 12:23 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-04 16:35 David Rientjes
2009-05-04 16:35 ` [patch 2/5] oom: fix possible android low memory killer NULL pointer David Rientjes
2009-05-04 16:35 ` [patch 3/5] oom: fix possible oom_dump_tasks " David Rientjes
2009-05-04 16:35 ` [patch 4/5] oom: move oom_adj value from task_struct to mm_struct David Rientjes
2009-05-04 16:35 ` [patch 5/5] oom: prevent possible OOM_DISABLE livelock David Rientjes
2009-05-04 21:48 ` [patch 1/5] oom: cleanup android low memory killer Arve Hjønnevåg
2009-05-04 22:09   ` Greg KH
2009-05-04 22:24     ` [PATCH 1/2] lowmemorykiller: Only iterate over process list when needed Arve Hjønnevåg
2009-05-04 22:24       ` [PATCH 2/2] lowmemorykiller: Don't count free space unless it meets the specified limit by itself Arve Hjønnevåg
2009-05-04 22:35     ` [patch 1/5] oom: cleanup android low memory killer David Rientjes
2009-05-04 22:59       ` Greg KH
2009-05-04 23:12         ` David Rientjes
2009-05-04 23:16           ` Greg KH
2009-05-04 23:36             ` Arve Hjønnevåg
2009-05-04 23:59             ` David Rientjes
2009-05-04 23:32           ` Rik van Riel
2009-05-11 19:44             ` David Rientjes
2009-05-14 12:23               ` KOSAKI Motohiro [this message]

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=20090514211934.F5B3.A69D9226@jp.fujitsu.com \
    --to=kosaki.motohiro@jp.fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=arve@android.com \
    --cc=greg@kroah.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=npiggin@suse.de \
    --cc=riel@redhat.com \
    --cc=rientjes@google.com \
    --cc=san@android.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

all inboxes | Powered by JetHome®