From: "Björn Töpel" <bjorn.topel@gmail.com>
To: Jonathan Lemon <jonathan.lemon@gmail.com>
Cc: Netdev <netdev@vger.kernel.org>,
"Kernel Team" <kernel-team@fb.com>,
"Björn Töpel" <bjorn.topel@intel.com>,
"Karlsson, Magnus" <magnus.karlsson@intel.com>,
"Alexei Starovoitov" <ast@kernel.org>,
"Daniel Borkmann" <daniel@iogearbox.net>
Subject: Re: [PATCH v4 bpf-next 0/2] Better handling of xskmap entries
Date: Tue, 4 Jun 2019 08:06:28 +0200 [thread overview]
Message-ID: <CAJ+HfNgtQ20Hpag8Y_rmBttrKOxZXGAeLS3ELLr_41+GXsv_7Q@mail.gmail.com> (raw)
In-Reply-To: <20190603163852.2535150-1-jonathan.lemon@gmail.com>
On Mon, 3 Jun 2019 at 19:49, Jonathan Lemon <jonathan.lemon@gmail.com> wrote:
>
> v3->v4:
> - Clarify error handling path.
>
> v2->v3:
> - Use correct map type.
>
> Jonathan Lemon (2):
> bpf: Allow bpf_map_lookup_elem() on an xskmap
> libbpf: remove qidconf and better support external bpf programs.
>
Nice work!
For the series,
Acked-by: Björn Töpel <bjorn.topel@intel.com>
> include/net/xdp_sock.h | 6 +-
> kernel/bpf/verifier.c | 6 +-
> kernel/bpf/xskmap.c | 4 +-
> tools/lib/bpf/xsk.c | 103 +++++-------------
> .../bpf/verifier/prevent_map_lookup.c | 15 ---
> 5 files changed, 39 insertions(+), 95 deletions(-)
>
> --
> 2.17.1
>
prev parent reply other threads:[~2019-06-04 6:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-03 16:38 [PATCH v4 bpf-next 0/2] Better handling of xskmap entries Jonathan Lemon
2019-06-03 16:38 ` [PATCH v4 bpf-next 1/2] bpf: Allow bpf_map_lookup_elem() on an xskmap Jonathan Lemon
2019-06-04 14:54 ` Daniel Borkmann
2019-06-04 15:30 ` Daniel Borkmann
2019-06-04 16:43 ` Jesper Dangaard Brouer
2019-06-04 17:25 ` Jonathan Lemon
2019-06-04 18:12 ` Martin Lau
2019-06-05 8:45 ` Björn Töpel
2019-06-05 15:42 ` Jonathan Lemon
2019-06-04 18:18 ` Björn Töpel
2019-06-04 20:07 ` Toke Høiland-Jørgensen
2019-06-03 16:38 ` [PATCH v4 bpf-next 2/2] libbpf: remove qidconf and better support external bpf programs Jonathan Lemon
2019-06-04 6:06 ` Björn Töpel [this message]
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=CAJ+HfNgtQ20Hpag8Y_rmBttrKOxZXGAeLS3ELLr_41+GXsv_7Q@mail.gmail.com \
--to=bjorn.topel@gmail.com \
--cc=ast@kernel.org \
--cc=bjorn.topel@intel.com \
--cc=daniel@iogearbox.net \
--cc=jonathan.lemon@gmail.com \
--cc=kernel-team@fb.com \
--cc=magnus.karlsson@intel.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).