lkml.org 
[lkml]   [2022]   [Jan]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH v6 6/9] mm: multigenerational lru: aging
On Tue 04-01-22 13:22:25, Yu Zhao wrote:
[...]
> +static void lru_gen_age_node(struct pglist_data *pgdat, struct scan_control *sc)
> +{
> + struct mem_cgroup *memcg;
> + bool success = false;
> + unsigned long min_ttl = READ_ONCE(lru_gen_min_ttl);
> +
> + VM_BUG_ON(!current_is_kswapd());
> +
> + current->reclaim_state->mm_walk = &pgdat->mm_walk;
> +
> + memcg = mem_cgroup_iter(NULL, NULL, NULL);
> + do {
> + struct lruvec *lruvec = mem_cgroup_lruvec(memcg, pgdat);
> +
> + if (age_lruvec(lruvec, sc, min_ttl))
> + success = true;
> +
> + cond_resched();
> + } while ((memcg = mem_cgroup_iter(NULL, memcg, NULL)));
> +
> + if (!success && mutex_trylock(&oom_lock)) {
> + struct oom_control oc = {
> + .gfp_mask = sc->gfp_mask,
> + .order = sc->order,
> + };
> +
> + if (!oom_reaping_in_progress())
> + out_of_memory(&oc);
> +
> + mutex_unlock(&oom_lock);
> + }

Why do you need to trigger oom killer from this path? Why cannot you
rely on the page allocator to do that like we do now?
--
Michal Hocko
SUSE Labs

\
 
 \ /
  Last update: 2022-01-07 14:13    [W:1.015 / U:0.032 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site