From: Denis Kirjanov <kda@linux-powerpc.org>
To: netdev@vger.kernel.org
Cc: brouer@redhat.com, jgross@suse.com, wei.liu@kernel.org,
paul@xen.org, ilias.apalodimas@linaro.org
Subject: [PATCH net-next v10 0/3] xen networking: add XDP support to xen-netfront
Date: Mon, 22 Jun 2020 12:21:09 +0300 [thread overview]
Message-ID: <1592817672-2053-1-git-send-email-kda@linux-powerpc.org> (raw)
The first patch adds a new extra type to enable proper synchronization
between an RX request/response pair.
The second patch implements BFP interface for xen-netfront.
The third patch enables extra space for XDP processing.
v10:
- add a new xen_netif_extra_info type to enable proper synchronization
between an RX request/response pair.
- order local variable declarations
v9:
- assign an xdp program before switching to Reconfiguring
- minor cleanups
- address checkpatch issues
v8:
- add PAGE_POOL config dependency
- keep the state of XDP processing in netfront_xdp_enabled
- fixed allocator type in xdp_rxq_info_reg_mem_model()
- minor cleanups in xen-netback
v7:
- use page_pool_dev_alloc_pages() on page allocation
- remove the leftover break statement from netback_changed
v6:
- added the missing SOB line
- fixed subject
v5:
- split netfront/netback changes
- added a sync point between backend/frontend on switching to XDP
- added pagepool API
v4:
- added verbose patch descriprion
- don't expose the XDP headroom offset to the domU guest
- add a modparam to netback to toggle XDP offset
- don't process jumbo frames for now
v3:
- added XDP_TX support (tested with xdping echoserver)
- added XDP_REDIRECT support (tested with modified xdp_redirect_kern)
- moved xdp negotiation to xen-netback
v2:
- avoid data copying while passing to XDP
- tell xen-netback that we need the headroom space
Denis Kirjanov (3):
xen: netif.h: add a new extra type for XDP
xen networking: add basic XDP support for xen-netfront
xen networking: add XDP offset adjustment to xen-netback
drivers/net/Kconfig | 1 +
drivers/net/xen-netback/common.h | 4 +
drivers/net/xen-netback/interface.c | 2 +
drivers/net/xen-netback/netback.c | 7 +
drivers/net/xen-netback/rx.c | 15 +-
drivers/net/xen-netback/xenbus.c | 32 ++++
drivers/net/xen-netfront.c | 332 ++++++++++++++++++++++++++++++++++--
include/xen/interface/io/netif.h | 18 +-
8 files changed, 399 insertions(+), 12 deletions(-)
--
1.8.3.1
next reply other threads:[~2020-06-22 9:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-22 9:21 Denis Kirjanov [this message]
2020-06-22 9:21 ` [PATCH net-next v10 1/3] xen: netif.h: add a new extra type for XDP Denis Kirjanov
2020-06-22 9:21 ` [PATCH net-next v10 2/3] xen networking: add basic XDP support for xen-netfront Denis Kirjanov
2020-06-22 9:58 ` Jesper Dangaard Brouer
2020-06-22 12:45 ` Denis Kirjanov
2020-06-22 13:28 ` Jesper Dangaard Brouer
2020-06-22 14:27 ` Denis Kirjanov
2020-06-22 12:34 ` kernel test robot
2020-06-22 9:21 ` [PATCH net-next v10 3/3] xen networking: add XDP offset adjustment to xen-netback Denis Kirjanov
2020-06-22 10:10 ` Paul Durrant
2020-06-22 12:50 ` Denis Kirjanov
2020-06-22 14:56 ` Paul Durrant
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=1592817672-2053-1-git-send-email-kda@linux-powerpc.org \
--to=kda@linux-powerpc.org \
--cc=brouer@redhat.com \
--cc=ilias.apalodimas@linaro.org \
--cc=jgross@suse.com \
--cc=netdev@vger.kernel.org \
--cc=paul@xen.org \
--cc=wei.liu@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).