On 05/21/2019 04:04 PM, Michal Hocko wrote: > On Tue 21-05-19 08:25:55, Anshuman Khandual wrote: >> On 05/20/2019 10:29 PM, Tim Murray wrote: > [...] >>> not seem to introduce a noticeable hot start penalty, not does it >>> cause an increase in performance problems later in the app's >>> lifecycle. I've measured with and without process_madvise, and the >>> differences are within our noise bounds. Second, because we're not >> >> That is assuming that post process_madvise() working set for the application is >> always smaller. There is another challenge. The external process should ideally >> have the knowledge of active areas of the working set for an application in >> question for it to invoke process_madvise() correctly to prevent such scenarios. > > But that doesn't really seem relevant for the API itself, right? The > higher level logic the monitor's business. Right. I was just wondering how the monitor would even decide what areas of the target application is active or inactive. The target application is still just an opaque entity for the monitor unless there is some sort of communication. But you are right, this not relevant to the API itself.
