From: Andrii Nakryiko <andrii.nakryiko@gmail.com>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: Alexei Starovoitov <ast@kernel.org>, Martin Lau <kafai@fb.com>,
bpf@vger.kernel.org, Networking <netdev@vger.kernel.org>
Subject: Re: [PATCH bpf 0/3] BPF LRU map fix
Date: Tue, 14 May 2019 10:24:38 -0700 [thread overview]
Message-ID: <CAEf4BzaSj9Nh+2gcEJyBDzwgbaYWAUiQ7JWAez9+jDneCA6ZFQ@mail.gmail.com> (raw)
In-Reply-To: <cover.1557789256.git.daniel@iogearbox.net>
On Mon, May 13, 2019 at 4:19 PM Daniel Borkmann <daniel@iogearbox.net> wrote:
>
> This set fixes LRU map eviction in combination with map lookups out
> of system call side from user space. Main patch is the second one and
> test cases are adapted and added in the last one. Thanks!
>
> Daniel Borkmann (3):
> bpf: add map_lookup_elem_sys_only for lookups from syscall side
> bpf, lru: avoid messing with eviction heuristics upon syscall lookup
> bpf: test ref bit from data path and add new tests for syscall path
>
> include/linux/bpf.h | 1 +
> kernel/bpf/hashtab.c | 23 ++-
> kernel/bpf/syscall.c | 5 +-
> tools/testing/selftests/bpf/test_lru_map.c | 288 +++++++++++++++++++++++++++--
> 4 files changed, 297 insertions(+), 20 deletions(-)
>
> --
> 2.9.5
>
For the series:
Acked-by: Andrii Nakryiko <andriin@fb.com>
next prev parent reply other threads:[~2019-05-14 17:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 23:18 [PATCH bpf 0/3] BPF LRU map fix Daniel Borkmann
2019-05-13 23:18 ` [PATCH bpf 1/3] bpf: add map_lookup_elem_sys_only for lookups from syscall side Daniel Borkmann
2019-05-14 5:04 ` Andrii Nakryiko
2019-05-14 7:59 ` Daniel Borkmann
2019-05-14 16:34 ` Andrii Nakryiko
2019-05-13 23:18 ` [PATCH bpf 2/3] bpf, lru: avoid messing with eviction heuristics upon syscall lookup Daniel Borkmann
2019-05-13 23:18 ` [PATCH bpf 3/3] bpf: test ref bit from data path and add new tests for syscall path Daniel Borkmann
2019-05-14 17:24 ` Andrii Nakryiko [this message]
2019-05-14 17:56 ` [PATCH bpf 0/3] BPF LRU map fix Alexei Starovoitov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAEf4BzaSj9Nh+2gcEJyBDzwgbaYWAUiQ7JWAez9+jDneCA6ZFQ@mail.gmail.com \
--to=andrii.nakryiko@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kafai@fb.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).