From: Lorenzo Bianconi <lorenzo@kernel.org>
To: bpf@vger.kernel.org, netdev@vger.kernel.org
Cc: davem@davemloft.net, kuba@kernel.org, ast@kernel.org,
daniel@iogearbox.net, brouer@redhat.com,
lorenzo.bianconi@redhat.com, alexander.duyck@gmail.com,
maciej.fijalkowski@intel.com, saeed@kernel.org
Subject: [PATCH v2 bpf-next 0/2] introduce xdp_init_buff/xdp_prepare_buff
Date: Fri, 11 Dec 2020 20:28:11 +0100 [thread overview]
Message-ID: <cover.1607714335.git.lorenzo@kernel.org> (raw)
Introduce xdp_init_buff and xdp_prepare_buff utility routines to initialize
xdp_buff data structure and remove duplicated code in all XDP capable
drivers.
Changes since v1:
- introduce xdp_prepare_buff utility routine
Lorenzo Bianconi (2):
net: xdp: introduce xdp_init_buff utility routine
net: xdp: introduce xdp_prepare_buff utility routine
drivers/net/ethernet/amazon/ena/ena_netdev.c | 8 +++-----
drivers/net/ethernet/broadcom/bnxt/bnxt_xdp.c | 7 ++-----
.../net/ethernet/cavium/thunder/nicvf_main.c | 11 ++++++-----
.../net/ethernet/freescale/dpaa/dpaa_eth.c | 10 ++++------
.../net/ethernet/freescale/dpaa2/dpaa2-eth.c | 13 +++++--------
drivers/net/ethernet/intel/i40e/i40e_txrx.c | 18 +++++++++---------
drivers/net/ethernet/intel/ice/ice_txrx.c | 17 +++++++++--------
drivers/net/ethernet/intel/igb/igb_main.c | 18 +++++++++---------
drivers/net/ethernet/intel/ixgbe/ixgbe_main.c | 19 +++++++++----------
.../net/ethernet/intel/ixgbevf/ixgbevf_main.c | 19 +++++++++----------
drivers/net/ethernet/marvell/mvneta.c | 9 +++------
.../net/ethernet/marvell/mvpp2/mvpp2_main.c | 13 +++++++------
drivers/net/ethernet/mellanox/mlx4/en_rx.c | 8 +++-----
.../net/ethernet/mellanox/mlx5/core/en_rx.c | 7 ++-----
.../ethernet/netronome/nfp/nfp_net_common.c | 12 ++++++------
drivers/net/ethernet/qlogic/qede/qede_fp.c | 7 ++-----
drivers/net/ethernet/sfc/rx.c | 9 +++------
drivers/net/ethernet/socionext/netsec.c | 8 +++-----
drivers/net/ethernet/ti/cpsw.c | 17 ++++++-----------
drivers/net/ethernet/ti/cpsw_new.c | 17 ++++++-----------
drivers/net/hyperv/netvsc_bpf.c | 7 ++-----
drivers/net/tun.c | 11 ++++-------
drivers/net/veth.c | 14 +++++---------
drivers/net/virtio_net.c | 18 ++++++------------
drivers/net/xen-netfront.c | 8 +++-----
include/net/xdp.h | 17 +++++++++++++++++
net/bpf/test_run.c | 9 +++------
net/core/dev.c | 18 ++++++++----------
28 files changed, 154 insertions(+), 195 deletions(-)
--
2.29.2
next reply other threads:[~2020-12-11 21:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-11 19:28 Lorenzo Bianconi [this message]
2020-12-11 19:28 ` [PATCH v2 bpf-next 1/2] net: xdp: introduce xdp_init_buff utility routine Lorenzo Bianconi
2020-12-11 19:28 ` [PATCH v2 bpf-next 2/2] net: xdp: introduce xdp_prepare_buff " Lorenzo Bianconi
2020-12-12 1:00 ` Saeed Mahameed
2020-12-12 14:34 ` Lorenzo Bianconi
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=cover.1607714335.git.lorenzo@kernel.org \
--to=lorenzo@kernel.org \
--cc=alexander.duyck@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=brouer@redhat.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=lorenzo.bianconi@redhat.com \
--cc=maciej.fijalkowski@intel.com \
--cc=netdev@vger.kernel.org \
--cc=saeed@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).