[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e88fe274-cd53-40d4-9a8e-7c6a4e1d8c44@vivo.com>
Date: Wed, 13 Sep 2023 09:18:55 +0800
From: Bixuan Cui <cuibixuan@...o.com>
To: Chuyi Zhou <zhouchuyi@...edance.com>, 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,
Michal Hocko <mhocko@...e.com>
Subject: Re: [RFC PATCH v2 1/5] mm, oom: Introduce bpf_oom_evaluate_task
在 2023/8/10 16:13, Chuyi Zhou 写道:
> +#include <linux/bpf.h> #include <linux/oom.h> #include <linux/mm.h>
> #include <linux/err.h> @@ -305,6 +306,27 @@ static enum oom_constraint
> constrained_alloc(struct oom_control *oc) return CONSTRAINT_NONE; }
> +enum { + NO_BPF_POLICY, + BPF_EVAL_ABORT, + BPF_EVAL_NEXT, +
> BPF_EVAL_SELECT, +}; +
I saw that tools/testing/selftests/bpf/progs/oom_policy.c is also using
NO_BPF_POLICY etc. I think
+enum {
+ NO_BPF_POLICY,
+ BPF_EVAL_ABORT,
+ BPF_EVAL_NEXT,
+ BPF_EVAL_SELECT,
+};
+
definitions can be placed in include/linux/oom.h
Thanks
Bixuan Cui
Powered by blists - more mailing lists