[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9f6b8aaa-50b1-435b-a525-9a7986f63845@vivo.com>
Date: Fri, 15 Sep 2023 10:28:39 +0800
From: Bixuan Cui <cuibixuan@...o.com>
To: Chuyi Zhou <zhouchuyi@...edance.com>,
Jonathan Corbet <corbet@....net>, hannes@...xchg.org,
mhocko@...nel.org, roman.gushchin@...ux.dev, ast@...nel.org,
daniel@...earbox.net, andrii@...nel.org, muchun.song@...ux.dev
Cc: bpf@...r.kernel.org, linux-kernel@...r.kernel.org,
wuyun.abel@...edance.com, robin.lu@...edance.com
Subject: Re: [External] Re: [RFC PATCH v2 2/5] mm: Add policy_name to identify
OOM policies
在 2023/9/14 20:50, Chuyi Zhou 写道:
>>
>> Delete set_oom_policy_name, it makes no sense for users to set policy
>> names. 🙂
>>
>
> There can be multiple OOM policy in the system at the same time.
>
> If we need to apply different OOM policies to different memcgs based on
> different scenarios, we can use this hook(set_oom_policy_name) to set
> name to identify which policy in invoked at that time.
>
> Just some thoughts.
Well, I thought the system would only load one OOM policy(set one policy
name), which would set the prio of all memcgs.
What you mean is that multiple bpf.c may be loaded at the system, and
each bpf.c sets the different policy for different memcgs?
Powered by blists - more mailing lists