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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 6 Mar 2014 16:13:37 -0500
From:	Tejun Heo <>
To:	David Rientjes <>
Cc:	Andrew Morton <>,
	Johannes Weiner <>,
	Michal Hocko <>,
	KAMEZAWA Hiroyuki <>,
	Christoph Lameter <>,
	Pekka Enberg <>,
	Mel Gorman <>, Oleg Nesterov <>,
	Rik van Riel <>,
	Jianguo Wu <>,
	Tim Hockin <>,,,,
Subject: Re: [patch 09/11] mm, page_alloc: allow system oom handlers to use
 memory reserves

On Tue, Mar 04, 2014 at 07:59:35PM -0800, David Rientjes wrote:
> The root memcg allows unlimited memory charging, so no memory may be
> reserved for userspace oom handlers that are responsible for dealing
> with system oom conditions.
> Instead, this memory must come from per-zone memory reserves.  This
> allows the memory allocation to succeed, and the memcg charge will
> naturally succeed afterwards.
> This patch introduces per-zone oom watermarks that aren't really
> watermarks in the traditional sense.  The oom watermark is the root
> memcg's oom reserve proportional to the size of the zone.  When a page
> allocation is done, the effective watermark is
> 	[min/low/high watermark] - [oom watermark]
> For the [min watermark] case, this is effectively the oom reserve.
> However, it also adjusts the low and high watermark accordingly so
> memory is actually only allocated from min reserves when appropriate.
> Signed-off-by: David Rientjes <>

Until consensus on the whole approach can be reached,

 Nacked-by: Tejun Heo <>


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists