linux-kernel - RE: [PATCH 3.2.0-rc1 2/3] MM hook for page allocation and release

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: <84FF21A720B0874AA94B46D76DB9826904554575@008-AM1MPN1-003.mgdnok.nokia.com>
Date:	Thu, 5 Jan 2012 15:17:26 +0000
From:	<leonid.moiseichuk@...ia.com>
To:	<riel@...hat.com>, <penberg@...nel.org>
CC:	<kamezawa.hiroyu@...fujitsu.com>, <linux-mm@...ck.org>,
	<linux-kernel@...r.kernel.org>, <cesarb@...arb.net>,
	<emunson@...bm.net>, <aarcange@...hat.com>, <mel@....ul.ie>,
	<rientjes@...gle.com>, <dima@...roid.com>, <gregkh@...e.de>,
	<rebecca@...roid.com>, <san@...gle.com>,
	<akpm@...ux-foundation.org>, <vesa.jaaskelainen@...ia.com>
Subject: RE: [PATCH 3.2.0-rc1 2/3] MM hook for page allocation and release

Huh,
Early notification not much better then late. Cache size impacts mostly user-space responsiveness, so cache is accounted as free memory but device need be tuned development time according how fast it should be in different device-specific use-cases (it depends from zillions technical and non-technical factors e.g.  producer needs).
I fixed all known findings and trying to find places to integrate into vmscan/page-writeback as Pekka has advised. 

With Best Wishes,
Leonid

-----Original Message-----
From: ext Rik van Riel [mailto:riel@...hat.com] 
Sent: 05 January, 2012 17:05
To: Pekka Enberg
Cc: Moiseichuk Leonid (Nokia-MP/Helsinki); kamezawa.hiroyu@...fujitsu.com; linux-mm@...ck.org; linux-kernel@...r.kernel.org; cesarb@...arb.net; emunson@...bm.net; aarcange@...hat.com; mel@....ul.ie; rientjes@...gle.com; dima@...roid.com; gregkh@...e.de; rebecca@...roid.com; san@...gle.com; akpm@...ux-foundation.org; Jaaskelainen Vesa (Nokia-MP/Helsinki)
Subject: Re: [PATCH 3.2.0-rc1 2/3] MM hook for page allocation and release

On 01/05/2012 07:49 AM, Pekka Enberg wrote:
> On Thu, Jan 5, 2012 at 1:26 PM,<leonid.moiseichuk@...ia.com>  wrote:
>> I agree that hooking alloc_pages is ugly way. So alternatives I see:
>>
>> - shrinkers (as e.g. Android OOM used) but shrink_slab called only 
>> from try_to_free_pages only if we are on slow reclaim path on memory 
>> allocation, so it cannot be used for e.g. 75% memory tracking or when 
>> pages released to notify user space that we are OK. But according to 
>> easy to use it will be the best approach.

Well, there is always the page cache.

If, at reclaim time, the amount of page cache + free memory is below the free threshold, we should still have space left to handle userspace things.

It may be possible to hijack memcg accounting to get lower usage thresholds for earlier notification.  That way the code can stay out of the true fast paths like alloc_pages.

--
All rights reversed