On Wed, 2023-01-25 at 14:01 +0100, Michal Hocko wrote: > > I have read through your cover letter and it talks about the > interface > but it doesn't really talk about usecases and how they are supposed > to > use this feature - except the prctl based flag gets inherited. So > could > you elaborate some more about those usecases please? I can explain a little about the use case. There are people who use forked (rather than threaded) servers for certain workloads, from a garbage collected language without pointers, which means madvise simply cannot be made available in that language. The people running that workload have experimented with uKSM in the past, and seen about a 20% capacity increase from doing that. Because madvise is not possible in that programming language, and the addresses of data keep moving around as things get garbage collected, KSM sharing needs to be enabled "from the outside" for that workload. prctl seems like a good way to do that. -- All Rights Reversed.
Attachment:
signature.asc
Description: This is a digitally signed message part
