linux-kernel - Re: Android low memory killer vs. memory pressure notifications

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 for Android: free password hash cracker in your pocket

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

Message-ID: <alpine.DEB.2.00.1112201322170.22077@chino.kir.corp.google.com>
Date:	Tue, 20 Dec 2011 13:36:00 -0800 (PST)
From:	David Rientjes <rientjes@...gle.com>
To:	Anton Vorontsov <anton.vorontsov@...aro.org>
cc:	Michal Hocko <mhocko@...e.cz>,
	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
	Arve Hjønnevåg <arve@...roid.com>,
	Rik van Riel <riel@...hat.com>, Pavel Machek <pavel@....cz>,
	Greg Kroah-Hartman <gregkh@...e.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	John Stultz <john.stultz@...aro.org>, linux-mm@...ck.org,
	linux-kernel@...r.kernel.org, Johannes Weiner <hannes@...xchg.org>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
Subject: Re: Android low memory killer vs. memory pressure notifications

On Tue, 20 Dec 2011, Anton Vorontsov wrote:

> Hm, assuming that metadata is no longer an issue, why do you think avoiding
> cgroups would be a good idea?
> 

It's helpful for certain end users, particularly those in the embedded 
world, to be able to disable as many config options as possible to reduce 
the size of kernel image as much as possible, so they'll want a minimal 
amount of kernel functionality that allows such notifications.  Keep in 
mind that CONFIG_CGROUP_MEM_RES_CTLR is not enabled by default because of 
this (enabling it, CONFIG_RESOURCE_COUNTERS, and CONFIG_CGROUPS increases 
the size of the kernel text by ~1%), and it's becoming increasingly 
important for certain workloads to be notified of low memory conditions 
without any restriction on its usage other than the amount of RAM that the 
system has so that they can trigger internal memory freeing, explicit 
memory compaction from the command line, drop caches, reducing scheduling 
priority, etc.
--
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/