[6.6] [Bugfix] mm: rework refault detection · Pull Request !4831 · anolis/cloud-kernel

bugzilla: https://bugzilla.openanolis.cn/show_bug.cgi?id=19589

With anon and file min_seq being able to move independently, rework                           │
    workingset protection as well so that the comparison of refaults between                      │        rcu_read_lock();
    anon and file is always on an equal footing.                                                  │
                                                                                                  │-       recent = lru_gen_test_recent(shadow, type, &lruvec, &token, &workingset);
    Specifically, make lru_gen_test_recent() return true for refaults                             │+       recent = lru_gen_test_recent(shadow, &lruvec, &token, &workingset);
    happening within the distance of MAX_NR_GENS.  For example, if min_seq of                     │        if (lruvec != folio_lruvec(folio))
    a type is max_seq-MIN_NR_GENS, refaults from min_seq-1, i.e.,                                 │                goto unlock;
    max_seq-MIN_NR_GENS-1, are also considered recent, since the distance                         │
    max_seq-(max_seq-MIN_NR_GENS-1), i.e., MIN_NR_GENS+1 is less than                             │@@ -330,7 +332,7 @@ static void *lru_gen_eviction(struct folio *folio)
    MAX_NR_GENS.                                                                                  │        return NULL;
                                                                                                  │ }
    As an intermediate step to the final optimization, this change by itself                      │
    should not have userspace-visiable effects beyond performance.

类型	指派人员	状态
审查	zhongjiang vxuyu baolin.wang	已完成 (0/0人)
测试	小龙已测试通过	已完成 (1/1人)

GVPanolis/cloud-kernel

搜索帮助

GVP anolis/cloud-kernel