netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Lemon <jonathan.lemon@gmail.com>
To: <netdev@vger.kernel.org>
Cc: <kernel-team@fb.com>, <bjorn.topel@intel.com>,
	<magnus.karlsson@intel.com>
Subject: [PATCH v3 bpf-next 0/2] Better handling of xskmap entries
Date: Fri, 31 May 2019 11:57:03 -0700	[thread overview]
Message-ID: <20190531185705.2629959-1-jonathan.lemon@gmail.com> (raw)

Respin of v2 to fix stupid error.

Testing with samples/bpf/xdpsock:
[root@kerneltest004.06.atn2 ~]# ./xdpsock  -i eth0 -q 0

 sock0@eth0:0 rxdrop	
                pps         pkts        1.00       
rx              17          17         
tx              0           0          


Jonathan Lemon (2):
  bpf: Allow bpf_map_lookup_elem() on an xskmap
  libbpf: remove qidconf and better support external bpf programs.

 include/net/xdp_sock.h                        |  6 +-
 kernel/bpf/verifier.c                         |  6 +-
 kernel/bpf/xskmap.c                           |  4 +-
 tools/lib/bpf/xsk.c                           | 79 ++++---------------
 .../bpf/verifier/prevent_map_lookup.c         | 15 ----
 5 files changed, 27 insertions(+), 83 deletions(-)

-- 
2.17.1


             reply	other threads:[~2019-05-31 18:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-31 18:57 Jonathan Lemon [this message]
2019-05-31 18:57 ` [PATCH v3 bpf-next 1/2] bpf: Allow bpf_map_lookup_elem() on an xskmap Jonathan Lemon
2019-06-01 23:06   ` Song Liu
2019-05-31 18:57 ` [PATCH v3 bpf-next 2/2] libbpf: remove qidconf and better support external bpf programs Jonathan Lemon
2019-06-01 23:05   ` Song Liu
2019-06-02  4:18     ` Jonathan Lemon
2019-06-02  6:55       ` Song Liu
2019-06-03 11:11       ` Björn Töpel

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=20190531185705.2629959-1-jonathan.lemon@gmail.com \
    --to=jonathan.lemon@gmail.com \
    --cc=bjorn.topel@intel.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).