From: Magnus Karlsson <magnus.karlsson@intel.com>
To: magnus.karlsson@intel.com, bjorn.topel@intel.com, ast@kernel.org,
daniel@iogearbox.net, netdev@vger.kernel.org
Subject: [PATCH bpf-next 0/3] xsk: misc code cleanup
Date: Thu, 30 Aug 2018 15:56:40 +0200 [thread overview]
Message-ID: <1535637403-14549-1-git-send-email-magnus.karlsson@intel.com> (raw)
This patch set cleans up two code style issues with the xsk zero-copy
code. The resulting code is smaller and simpler.
Patch 1: Removes a potential compiler warning reported by the Intel
0-DAY kernel test infrastructure.
Patches 2-3: Removes the xdp_umem_props structure. At some point, it
was used to break a dependency, but the members are these
days much better off in the xdp_umem since the dependency
does not exist anymore.
I based this patch set on bpf-next commit 234dbe3dc1db ("Merge branch
'verifier-liveness-simplification'")
Thanks: Magnus
Magnus Karlsson (3):
i40e: fix possible compiler warning in xsk TX path
xsk: get rid of useless struct xdp_umem_props
i40e: adapt driver to new xdp_umem structure
drivers/net/ethernet/intel/i40e/i40e_xsk.c | 10 ++++------
include/net/xdp_sock.h | 8 ++------
net/xdp/xdp_umem.c | 4 ++--
net/xdp/xdp_umem_props.h | 14 --------------
net/xdp/xsk.c | 10 ++++++----
net/xdp/xsk_queue.c | 5 +++--
net/xdp/xsk_queue.h | 13 +++++++------
7 files changed, 24 insertions(+), 40 deletions(-)
delete mode 100644 net/xdp/xdp_umem_props.h
next reply other threads:[~2018-08-30 17:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-30 13:56 Magnus Karlsson [this message]
2018-08-30 13:56 ` [PATCH bpf-next 1/3] i40e: fix possible compiler warning in xsk TX path Magnus Karlsson
2018-08-30 13:56 ` [PATCH bpf-next 2/3] xsk: get rid of useless struct xdp_umem_props Magnus Karlsson
2018-08-31 4:03 ` kbuild test robot
2018-08-30 13:56 ` [PATCH bpf-next 3/3] i40e: adapt driver to new xdp_umem structure Magnus Karlsson
2018-08-31 10:34 ` Daniel Borkmann
2018-08-31 2:42 ` [PATCH bpf-next 0/3] xsk: misc code cleanup 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=1535637403-14549-1-git-send-email-magnus.karlsson@intel.com \
--to=magnus.karlsson@intel.com \
--cc=ast@kernel.org \
--cc=bjorn.topel@intel.com \
--cc=daniel@iogearbox.net \
--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).