From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: dev@dpdk.org, ybrustin@cisco.com, tiwei.bie@intel.com,
jfreimann@redhat.com
Cc: stable@dpdk.org, Maxime Coquelin <maxime.coquelin@redhat.com>
Subject: [dpdk-dev] [PATCH v2 0/4] net/virtio: Fix packet segmentation bug
Date: Wed, 5 Jun 2019 10:10:01 +0200 [thread overview]
Message-ID: <20190605081005.15716-1-maxime.coquelin@redhat.com> (raw)
This series fixes a bug reported by Yaroslav, where segmented
packets miss some segments and head segment's data_len was set
to a wrong value.
Last patch is not a fix, but it removes some useless checks
in Rx paths.
Maxime Coquelin (4):
net/virtio: fix segmented packet issue in in-order Rx path
net/virtio: fix segmented packet issue in mergeable Rx path
net/virtio: fix segment data len in mergeable packed Rx path
net/virtio: remove useless pointers checks
drivers/net/virtio/virtio_rxtx.c | 24 ++++++------------------
1 file changed, 6 insertions(+), 18 deletions(-)
--
2.21.0
next reply other threads:[~2019-06-05 8:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 8:10 Maxime Coquelin [this message]
2019-06-05 8:10 ` [dpdk-dev] [PATCH v2 1/4] net/virtio: fix segmented packet issue in in-order Rx path Maxime Coquelin
2019-06-05 9:34 ` [dpdk-dev] [dpdk-stable] " David Marchand
2019-06-05 8:10 ` [dpdk-dev] [PATCH v2 2/4] net/virtio: fix segmented packet issue in mergeable " Maxime Coquelin
2019-06-05 9:34 ` [dpdk-dev] [dpdk-stable] " David Marchand
2019-06-05 8:10 ` [dpdk-dev] [PATCH v2 3/4] net/virtio: fix segment data len in mergeable packed " Maxime Coquelin
2019-06-05 9:34 ` [dpdk-dev] [dpdk-stable] " David Marchand
2019-06-05 8:10 ` [dpdk-dev] [PATCH v2 4/4] net/virtio: remove useless pointers checks Maxime Coquelin
2019-06-05 9:35 ` 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=20190605081005.15716-1-maxime.coquelin@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=dev@dpdk.org \
--cc=jfreimann@redhat.com \
--cc=stable@dpdk.org \
--cc=tiwei.bie@intel.com \
--cc=ybrustin@cisco.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).