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

[Rik van Riel]

On 01/05/2012 07:49 AM, Pekka Enberg wrote:
> On Thu, Jan 5, 2012 at 1:26 PM,<leonid.moiseichuk@xxxxxxxxx>  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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/