linux-kernel - Re: [PATCH v2] memcg: Add memory.pressure

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] [day] [month] [year] [list]

Date:	Fri, 22 Feb 2013 16:26:37 +0900
From:	Minchan Kim <minchan@...nel.org>
To:	Anton Vorontsov <anton@...msg.org>
Cc:	Tejun Heo <tj@...nel.org>, cgroups@...r.kernel.org,
	David Rientjes <rientjes@...gle.com>,
	Pekka Enberg <penberg@...nel.org>,
	Mel Gorman <mgorman@...e.de>,
	Glauber Costa <glommer@...allels.com>,
	Michal Hocko <mhocko@...e.cz>,
	"Kirill A. Shutemov" <kirill@...temov.name>,
	Kamezawa Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
	Luiz Capitulino <lcapitulino@...hat.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Greg Thelen <gthelen@...gle.com>,
	Leonid Moiseichuk <leonid.moiseichuk@...ia.com>,
	KOSAKI Motohiro <kosaki.motohiro@...il.com>,
	Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com>,
	John Stultz <john.stultz@...aro.org>, linux-mm@...ck.org,
	linux-kernel@...r.kernel.org, linaro-kernel@...ts.linaro.org,
	patches@...aro.org, kernel-team@...roid.com,
	Orna Agmon Ben-Yehuda <ladypine@...il.com>,
	Muli Ben-Yehuda <mulix@...ix.org>
Subject: Re: [PATCH v2] memcg: Add memory.pressure_level events

On Thu, Feb 21, 2013 at 10:55:52PM -0800, Anton Vorontsov wrote:
> On Fri, Feb 22, 2013 at 08:56:08AM +0900, Minchan Kim wrote:
> > [...] The my point is that you have a plan to support? Why I have a
> > question is that you said your goal is to replace lowmemory killer
> 
> In short: yes, of course, if the non-memcg interface will be in demand.
> 
> > but android don't have enabled CONFIG_MEMCG as you know well
> > so they should enable it for using just notifier? or they need another hack to
> > connect notifier to global thing?
> 
> A hack is not an option for me. :-) My final goal is to switch Android to
> use the notifier without need for hacks/external patches or
> drivers/staging.
> 
> But my current goal is to make the most generic case work, and do this in
> the most correct way. That is, vmpressure + MEMCG. Once I accomplish this,
> I can then think of any niche needs (such as Android).
> 
> There will be two possibilities for Android:
> 
> 1. Obviously, turn on CONFIG_MEMCG. We need to measure its effect on real
>    devices, and see if it makes sense. (Plus, maybe there are other uses
>    for MEMCG on Android?)

I'd like to see this one.

> 
> or
> 
> 2. Implement /sys/fs/cgroups/memory/memory.pressure_level interface
>    without MEMCG. Doing this will be really easy as we'll already have
>    vmpressure() core, and Android has CROUPS=y. But I do expect some
>    discussion like 'why don't you fix memcg instead?'. We'll have to
>    answer this question by looking back at '1.'

Of course.

> 
> Also note that cgroups vmpressure notifiers were tried by QEMU folks, and
> it seemed to be useful:
> 
>    http://lists.gnu.org/archive/html/qemu-devel/2012-12/msg02821.html 

I saw that.

> 
> So, nowadays it is not only about Android. Some time ago I also got an
> email from Orna Agmon Ben-Yehuda, who suggested to use vmpressure stuff
> with 'memcached' (but I didn't find time to actually try it, so far. :(
> Thanks for the email, btw!).

I also got received email from another people in embedded side about
memory notifier which I worked long time ago and I used to introduce
your work to them instead of my old solution.
It seems they don't use Android and has very small RAM so they want
to handle memory very efficiently. For such purpose, I hope vmpressure
become tiny and can support even NOMMU system.

> 
> So it is useful with or without MEMCG, and if we will really need to
> support vmpressure without MEMCG, I will have to implement the support in
> addition to MEMCG case, yes.

Thanks for your clarification.

> 
> Thanks,
> 
> Anton
> 
> --
> To unsubscribe, send a message with 'unsubscribe linux-mm' in
> the body to majordomo@...ck.org.  For more info on Linux MM,
> see: http://www.linux-mm.org/ .
> Don't email: <a href=mailto:"dont@...ck.org"> email@...ck.org </a>

-- 
Kind regards,
Minchan Kim
--
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/