On Mon, May 21, 2018 at 3:29 PM Dave Hansen <dave.hansen@xxxxxxxxx> wrote: > On 05/21/2018 03:20 PM, Daniel Colascione wrote: > >> 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? > I don't really know what you mean. I should have been more clear. I meant, in general, that processes can *already* ask the kernel to allocate memory on behalf of the process, and sometimes this memory can't be reclaimed without an OOM kill. (You can swap memfd/tmpfs contents, but for simplicity, imagine we're running without a pagefile.) > I know folks use memfd to figure out > how much memory pressure we are under. I guess that would trigger when > you consume lots of memory with VMAs. I think you're thinking of the VM pressure level special files, not memfd, which creates an anonymous tmpfs file. > VMAs are probably the most similar to things like page tables that are > kernel memory that can't be directly reclaimed, but do get freed at > OOM-kill-time. But, VMAs are a bit harder than page tables because > freeing a page worth of VMAs does not necessarily free an entire page. I don't understand. We can reclaim memory used by VMAs by killing the process or processes attached to the address space that owns those VMAs. The OOM killer should Just Work. Why do we have to have some special limit of VMA count?
