[lkml]   [2017]   [Nov]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] mm: disable `vm.max_map_count' sysctl limit
On Mon, Nov 27, 2017 at 11:12:32AM +0100, Michal Hocko wrote:
> On Sun 26-11-17 17:09:32, Mikael Pettersson wrote:
> > - Reaching the limit causes various memory management system calls to
> > fail with ENOMEM, which is a lie. Combined with the unpredictability
> > of the number of mappings in a process, especially when non-trivial
> > memory management or heavy file mapping is used, it can be difficult
> > to reproduce these events and debug them. It's also confusing to get
> > ENOMEM when you know you have lots of free RAM.


> Could you be more explicit about _why_ we need to remove this tunable?
> I am not saying I disagree, the removal simplifies the code but I do not
> really see any justification here.

I imagine he started seeing random syscalls failing with ENOMEM and
eventually tracked it down to this stupid limit we used to need.

 \ /
  Last update: 2017-11-27 17:23    [W:0.102 / U:0.376 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site