On Tue, Mar 16, 2021 at 02:44:31PM +0800, Huang, Ying wrote: > Yu Zhao <yuzhao@xxxxxxxxxx> writes: > > > On Tue, Mar 16, 2021 at 10:07:36AM +0800, Huang, Ying wrote: > >> Rik van Riel <riel@xxxxxxxxxxx> writes: > >> > >> > On Sat, 2021-03-13 at 00:57 -0700, Yu Zhao wrote: > >> > > >> >> +/* > >> >> + * After pages are faulted in, they become the youngest generation. > >> >> They must > >> >> + * go through aging process twice before they can be evicted. After > >> >> first scan, > >> >> + * their accessed bit set during initial faults are cleared and they > >> >> become the > >> >> + * second youngest generation. And second scan makes sure they > >> >> haven't been used > >> >> + * since the first. > >> >> + */ > >> > > >> > I have to wonder if the reductions in OOM kills and > >> > low-memory tab discards is due to this aging policy > >> > change, rather than from the switch to virtual scanning. > > > > There are no policy changes per se. The current page reclaim also > > scans a faulted-in page at least twice before it can reclaim it. > > That said, the new aging yields a better overall result because it > > discovers every page that has been referenced since the last scan, > > in addition to what Ying has mentioned. The current page scan stops > > stops once it finds enough candidates, which may seem more > > efficiently, but actually pays the price for not finding the best. > > > >> If my understanding were correct, the temperature of the processes is > >> considered in addition to that of the individual pages. That is, the > >> pages of the processes that haven't been scheduled after the previous > >> scanning will not be scanned. I guess that this helps OOM kills? > > > > Yes, that's correct. > > > >> If so, how about just take advantage of that information for OOM killing > >> and page reclaiming? For example, if a process hasn't been scheduled > >> for long time, just reclaim its private pages. > > > > This is how it works. Pages that haven't been scanned grow older > > automatically because those that have been scanned will be tagged with > > younger generation numbers. Eviction does bucket sort based on > > generation numbers and attacks the oldest. > > Sorry, my original words are misleading. What I wanted to say was that > is it good enough that > > - Do not change the core algorithm of current page reclaiming. > > - Add some new logic to reclaim the process private pages regardless of > the Accessed bits if the processes are not scheduled for some long > enough time. This can be done before the normal page reclaiming. This is a good idea, which being used on Android and Chrome OS. We call it per-process reclaim, and I've mentioned here: https://lore.kernel.org/linux-mm/YBkT6175GmMWBvw3@xxxxxxxxxx/ On Android, our most advanced simulation that generates memory pressure from realistic user behavior shows 18% fewer low-memory kills, which in turn reduces cold starts by 16%. This is on top of per-process reclaim, a predecessor of ``MADV_COLD`` and ``MADV_PAGEOUT``, against background apps. The patches landed not long a ago :) See mm/madvise.c > So this is an one small step improvement to the current page reclaiming > algorithm via taking advantage of the scheduler information. It's > clearly not sophisticated as your new algorithm, for example, the cold > pages in the hot processes will not be reclaimed in this stage. But it > can reduce the overhead of scanning too. The general problems with the direction of per-process reclaim: 1) we can't find the coldest pages, as you have mentioned. 2) we can't reach file pages accessed via file descriptors only, especially those caching config files that were read only once. 3) we can't reclaim lru pages and slab objects proportionally and therefore we leave many stale slab objects behind. 4) we have to be proactive, as you suggested (once again, you were right), and this has a serious problem: client's battery life can be affected. The scanning overhead is only one of the two major problems of the current page reclaim. The other problem is the granularity of the active/inactive (sizes). We stopped using them in making job scheduling decision a long time ago. I know another large internet company adopted a similar approach as ours, and I'm wondering how everybody else is coping with the discrepancy from those counters. > All in all, some of your ideas may help the original LRU algorithm too. > Or some can be experimented without replacing the original algorithm. > > But from another point of view, your solution can be seen as a kind of > improvement on top of the original LRU algorithm too. It moves the > recently accessed pages to kind of multiple active lists based on > scanning page tables directly (instead of reversely). We hope this series can be a framework or an infrastructure flexible enough that people can build their complex use cases upon, e.g., proactive reclaim (machine-wide, not per process), cold memory estimation (for job scheduling), AEP demotion, specifically, we want people to use it with what you and Dave are working on here: https://patchwork.kernel.org/project/linux-mm/cover/20210304235949.7922C1C3@xxxxxxxxxxxxxxxxxx/
