From: David Marchand <david.marchand@redhat.com>
To: dev@dpdk.org
Cc: maxime.coquelin@redhat.com, olivier.matz@6wind.com,
fbl@sysclose.org, i.maximets@ovn.org
Subject: [dpdk-dev] [PATCH 0/5] Offload flags fixes
Date: Thu, 1 Apr 2021 11:51:34 +0200 [thread overview]
Message-ID: <20210401095140.17946-1-david.marchand@redhat.com> (raw)
The important part is the last patch on vhost handling of offloading
requests coming from a virtio guest interface.
The rest are small fixes that I accumulated while reviewing the mbuf
offload flags.
On this last patch, it has the potential of breaking existing
applications using the vhost library (OVS being impacted).
I did not mark it for backport, but I am having second thoughts.
The vhost example has not been updated yet, as I wanted to send this
series first to get feedback before looking more into the example code.
--
David Marchand
David Marchand (5):
mbuf: mark old offload flag as deprecated
net/tap: do not touch Tx offload flags
net/virtio: do not touch Tx offload flags
net/virtio: refactor Tx offload helper
vhost: fix offload flags in Rx path
drivers/net/tap/rte_eth_tap.c | 17 ++-
drivers/net/virtio/virtio_rxtx.c | 7 +-
drivers/net/virtio/virtio_rxtx_packed_avx.h | 2 +-
drivers/net/virtio/virtio_rxtx_packed_neon.h | 2 +-
drivers/net/virtio/virtqueue.h | 81 +++++-----
examples/vhost/main.c | 6 +
lib/librte_mbuf/rte_mbuf_core.h | 3 +-
lib/librte_vhost/virtio_net.c | 148 ++++++++-----------
8 files changed, 123 insertions(+), 143 deletions(-)
--
2.23.0
next reply other threads:[~2021-04-01 9:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-01 9:51 David Marchand [this message]
2021-04-01 9:52 David Marchand
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=20210401095140.17946-1-david.marchand@redhat.com \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=fbl@sysclose.org \
--cc=i.maximets@ovn.org \
--cc=maxime.coquelin@redhat.com \
--cc=olivier.matz@6wind.com \
/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).