linux-kernel - Re: [patch 1/5] oom: cleanup android low memory killer

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 11 May 2009 12:44:16 -0700 (PDT)
From:	David Rientjes <rientjes@...gle.com>
To:	Rik van Riel <riel@...hat.com>
cc:	Greg KH <greg@...ah.com>,
	Arve Hjønnevåg <arve@...roid.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Nick Piggin <npiggin@...e.de>, San Mehat <san@...roid.com>,
	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
	linux-kernel@...r.kernel.org, Greg KH <gregkh@...e.de>
Subject: Re: [patch 1/5] oom: cleanup android low memory killer

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?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/