Hi Willy, On Thu, May 29, 2025 at 04:28:46PM +0100, Matthew Wilcox wrote: > On Thu, May 29, 2025 at 03:43:26PM +0100, Lorenzo Stoakes wrote: > > After discussions in various threads (Usama's series adding a new prctl() > > in [0], and a proposal to adapt process_madvise() to do the same - > > conception in [1] and RFC in [2]), it seems fairly clear that it would make > > sense to explore a dedicated API to explicitly allow for actions which > > affect the virtual address space as a whole. > > > > Also, Barry is implementing a feature (currently under RFC) which could > > additionally make use of this API (see [3]). > > I think the reason that you're having trouble coming up with a good > place to put these ideas is because they are all bad ideas. Do none of > them. Problem solved. > > People should put more effort into allocating THPs automatically and > monitoring where they're helping performance and where they're hurting > performance, Can you please expand on people putting more effort? Is it about workloads or maybe malloc implementations (tcmalloc, jemalloc) being more intelligent in managing their allocations/frees to keep more used memory in hugepage aligned regions? And conveying to kernel which regions they prefer hugepage backed and which they do not? Or something else? > instead of coming up with these baroque reasons to blame > the sysadmin for not having tweaked some magic knob. To me this is not about blaming sysadmin but more about sysadmin wanting more fine grained control on THP allocation policies for different workloads running in a multi-tenant environment.
