From: <leonid.moiseichuk@nokia.com>
To: riel@redhat.com, penberg@kernel.org
Cc: kamezawa.hiroyu@jp.fujitsu.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, cesarb@cesarb.net,
emunson@mgebm.net, aarcange@redhat.com, mel@csn.ul.ie,
rientjes@google.com, dima@android.com, gregkh@suse.de,
rebecca@android.com, san@google.com, akpm@linux-foundation.org,
vesa.jaaskelainen@nokia.com
Subject: RE: [PATCH 3.2.0-rc1 2/3] MM hook for page allocation and release
Date: Thu, 5 Jan 2012 15:17:26 +0000 [thread overview]
Message-ID: <84FF21A720B0874AA94B46D76DB9826904554575@008-AM1MPN1-003.mgdnok.nokia.com> (raw)
In-Reply-To: <4F05BC1F.7070009@redhat.com>
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@redhat.com]
Sent: 05 January, 2012 17:05
To: Pekka Enberg
Cc: Moiseichuk Leonid (Nokia-MP/Helsinki); kamezawa.hiroyu@jp.fujitsu.com; linux-mm@kvack.org; linux-kernel@vger.kernel.org; cesarb@cesarb.net; emunson@mgebm.net; aarcange@redhat.com; mel@csn.ul.ie; rientjes@google.com; dima@android.com; gregkh@suse.de; rebecca@android.com; san@google.com; akpm@linux-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@nokia.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
next prev parent reply other threads:[~2012-01-05 15:18 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 17:21 [PATCH 3.2.0-rc1 0/3] Used Memory Meter pseudo-device and related changes in MM Leonid Moiseichuk
2012-01-04 17:21 ` [PATCH 3.2.0-rc1 1/3] Making si_swapinfo exportable Leonid Moiseichuk
2012-01-04 17:21 ` [PATCH 3.2.0-rc1 2/3] MM hook for page allocation and release Leonid Moiseichuk
2012-01-04 20:40 ` Pekka Enberg
2012-01-05 6:59 ` KAMEZAWA Hiroyuki
2012-01-05 11:26 ` leonid.moiseichuk
2012-01-05 12:49 ` Pekka Enberg
2012-01-05 15:05 ` Rik van Riel
2012-01-05 15:17 ` leonid.moiseichuk [this message]
2012-01-05 15:22 ` Mel Gorman
2012-01-04 17:21 ` [PATCH 3.2.0-rc1 3/3] Used Memory Meter pseudo-device module Leonid Moiseichuk
2012-01-04 19:55 ` Greg KH
2012-01-09 9:58 ` leonid.moiseichuk
2012-01-09 10:09 ` David Rientjes
2012-01-09 10:19 ` leonid.moiseichuk
2012-01-09 20:55 ` David Rientjes
2012-01-11 12:46 ` leonid.moiseichuk
2012-01-11 21:44 ` David Rientjes
2012-01-12 8:32 ` leonid.moiseichuk
2012-01-12 20:54 ` David Rientjes
2012-01-13 9:34 ` leonid.moiseichuk
2012-01-13 11:06 ` David Rientjes
2012-01-13 11:51 ` leonid.moiseichuk
2012-01-13 21:35 ` David Rientjes
2012-01-04 19:56 ` [PATCH 3.2.0-rc1 0/3] Used Memory Meter pseudo-device and related changes in MM Greg KH
2012-01-04 20:17 ` Rik van Riel
2012-01-04 20:42 ` Pekka Enberg
2012-01-05 23:01 ` David Rientjes
2012-01-05 12:22 ` leonid.moiseichuk
2012-01-05 11:47 ` leonid.moiseichuk
2012-01-05 12:40 ` Pekka Enberg
2012-01-05 13:02 ` leonid.moiseichuk
2012-01-05 14:57 ` Greg KH
2012-01-05 16:13 ` leonid.moiseichuk
2012-01-05 23:10 ` David Rientjes
2012-01-09 8:27 ` leonid.moiseichuk
2012-01-06 0:26 ` KOSAKI Motohiro
2012-01-09 8:49 ` leonid.moiseichuk
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=84FF21A720B0874AA94B46D76DB9826904554575@008-AM1MPN1-003.mgdnok.nokia.com \
--to=leonid.moiseichuk@nokia.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=cesarb@cesarb.net \
--cc=dima@android.com \
--cc=emunson@mgebm.net \
--cc=gregkh@suse.de \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=penberg@kernel.org \
--cc=rebecca@android.com \
--cc=riel@redhat.com \
--cc=rientjes@google.com \
--cc=san@google.com \
--cc=vesa.jaaskelainen@nokia.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