[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <0D674EA5-3626-4885-9ADC-5B7847CC967D@linux.dev>
Date: Sun, 20 Mar 2022 09:58:06 -0700
From: Roman Gushchin <roman.gushchin@...ux.dev>
To: Yafang Shao <laoar.shao@...il.com>
Cc: ast@...nel.org, daniel@...earbox.net, andrii@...nel.org,
kafai@...com, songliubraving@...com, yhs@...com,
john.fastabend@...il.com, kpsingh@...nel.org,
netdev@...r.kernel.org, bpf@...r.kernel.org
Subject: Re: [PATCH] bpf: selftests: cleanup RLIMIT_MEMLOCK
> On Mar 19, 2022, at 11:08 PM, Yafang Shao <laoar.shao@...il.com> wrote:
>
> Since we have alread switched to memcg-based memory accouting and control,
> we don't need RLIMIT_MEMLOCK any more.
>
> Signed-off-by: Yafang Shao <laoar.shao@...il.com>
> Cc: Roman Gushchin <roman.gushchin@...ux.dev>
>
> ---
> RLIMIT_MEMLOCK is still used in bpftool and libbpf, but it may be useful
> for backward compatibility, so I don't cleanup them.
Hi Yafang!
As I remember, we haven’t cleaned selftests up with the same logic: it’s nice to be able to run the same version of tests on older kernels.
Thanks!
Powered by blists - more mailing lists