[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAEf4Bzbi56xvvT9sEQbMYN6Pa-Gqk-FJTyw+LYZGbwUs-S98TA@mail.gmail.com>
Date: Mon, 27 Jul 2020 22:56:21 -0700
From: Andrii Nakryiko <andrii.nakryiko@...il.com>
To: Roman Gushchin <guro@...com>
Cc: bpf <bpf@...r.kernel.org>, Networking <netdev@...r.kernel.org>,
Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>,
Kernel Team <kernel-team@...com>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH bpf-next v2 22/35] bpf: eliminate rlimit-based memory
accounting for bpf ringbuffer
On Mon, Jul 27, 2020 at 12:21 PM Roman Gushchin <guro@...com> wrote:
>
> Do not use rlimit-based memory accounting for bpf ringbuffer.
> It has been replaced with the memcg-based memory accounting.
>
> bpf_ringbuf_alloc() can't return anything except ERR_PTR(-ENOMEM)
> and a valid pointer, so to simplify the code make it return NULL
> in the first case. This allows to drop a couple of lines in
> ringbuf_map_alloc() and also makes it look similar to other memory
> allocating function like kmalloc().
>
> Signed-off-by: Roman Gushchin <guro@...com>
> ---
LGTM.
Acked-by: Andrii Nakryiko <andriin@...com>
> kernel/bpf/ringbuf.c | 24 ++++--------------------
> 1 file changed, 4 insertions(+), 20 deletions(-)
>
[...]
Powered by blists - more mailing lists