On Mon, May 21, 2018 at 3:12 PM Dave Hansen <dave.hansen@xxxxxxxxx> wrote: > On 05/21/2018 03:07 PM, Daniel Colascione wrote: > > Now let's return to max_map_count itself: what is it supposed to achieve? > > If we want to limit application kernel memory resource consumption, let's > > limit application kernel memory resource consumption, accounting for it on > > a byte basis the same way we account for other kernel objects allocated on > > behalf of userspace. Why should we have a separate cap just for the VMA > > count? > VMAs consume kernel memory and we can't reclaim them. That's what it > boils down to. How is it different from memfd in that respect?