[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <58167241-3a94-f905-e463-1d21a1268655@iogearbox.net>
Date: Tue, 20 Nov 2018 00:56:09 +0100
From: Daniel Borkmann <daniel@...earbox.net>
To: Lorenz Bauer <lmb@...udflare.com>, ast@...nel.org
Cc: netdev@...r.kernel.org, linux-api@...r.kernel.org,
songliubraving@...com
Subject: Re: [PATCH v3 0/4] bpf: allow zero-initialising hash map seed
On 11/16/2018 12:41 PM, Lorenz Bauer wrote:
> Allow forcing the seed of a hash table to zero, for deterministic
> execution during benchmarking and testing.
>
> Changes from v2:
> * Change ordering of BPF_F_ZERO_SEED in linux/bpf.h
>
> Comments adressed from v1:
> * Add comment to discourage production use to linux/bpf.h
> * Require CAP_SYS_ADMIN
>
> Lorenz Bauer (4):
> bpf: allow zero-initializing hash map seed
> bpf: move BPF_F_QUERY_EFFECTIVE after map flags
> tools: sync linux/bpf.h
> tools: add selftest for BPF_F_ZERO_SEED
>
> include/uapi/linux/bpf.h | 9 ++--
> kernel/bpf/hashtab.c | 13 ++++-
> tools/include/uapi/linux/bpf.h | 13 +++--
> tools/testing/selftests/bpf/test_maps.c | 68 +++++++++++++++++++++----
> 4 files changed, 84 insertions(+), 19 deletions(-)
>
Applied to bpf-next, thanks!
Powered by blists - more mailing lists