News for hackers. Stuff that matters.
Re:Disable transparent hugepages by zaarn on Tuesday November 28, 2017 @08:34AM (#15797050)
malloc() is higher level than what the kernel does.

At the lower syscall level you move the BRK address, which is the highest memory address you're allowed to use. By default this is just after the statically initialized memory.

malloc() is just a library that manages this memory for you.

Linux has no idea if you will use the memory you just allocated, usually this happens dynamically; when you access a memory region for the first time, it is allocated in memory for real.

Re:Disable transparent hugepages by myst on Tuesday November 28, 2017 @09:03AM (#15797327)
Modern allocators use mmap(2).
Re:Disable transparent hugepages by zaarn on Tuesday November 28, 2017 @09:09AM (#15797388)
They do? Quite interesting. Tho it shouldn't really change the underlying mechanism; map only pages the process has touched.
Re:Disable transparent hugepages by aduitsis on Tuesday November 28, 2017 @09:13AM (#15797432)
May add, if you mmap(2) a memory segment (even a very large one, say 1Tb), nothing happens with regard to page mapping. It is not uncommon to see java tomcat processes allocating north of 80 Gb. But only a small percentage of these is actually used.
Re:Disable transparent hugepages by loeg on Tuesday November 28, 2017 @12:41PM (#15799450)
Well, the page tables are initialized. Those aren't totally free, especially if a large mapping uses 4k pages.