From: Cody Doucette <doucette@bu.edu>
Cc: dev@dpdk.org, Cody Doucette <doucette@bu.edu>
Subject: [dpdk-dev] [PATCH v5 0/3] Extend rte_ipv6_frag_get_ipv6_fragment_header()
Date: Wed, 31 Oct 2018 02:17:55 +0000 [thread overview]
Message-ID: <20181031021758.66752-1-doucette@bu.edu> (raw)
Extend rte_ipv6_frag_get_ipv6_fragment_header() to skip over any
other IPv6 extension headers when finding the fragment header.
---
v5:
* Removed duplicate patch from submission.
v4:
* Separated into multiple patches and added cover letter.
v3:
* Removed compilation flag D_XOPEN_SOURCE=700 from the
failsafe driver to allow compilation on freebsd.
v2:
* Moved IPv6 extension header definitions to lib_net.
Cody Doucette (3):
net/failsafe: remove D_XOPEN_SOURCE flag
net: add IPv6 extension header definitions
ip_frag: extend IPv6 fragment header retrieval
drivers/net/failsafe/Makefile | 1 -
drivers/net/failsafe/meson.build | 1 -
examples/ip_reassembly/main.c | 6 ++--
lib/librte_ip_frag/rte_ip_frag.h | 23 ++++++-------
lib/librte_ip_frag/rte_ip_frag_version.map | 1 +
lib/librte_ip_frag/rte_ipv6_fragmentation.c | 38 +++++++++++++++++++++
lib/librte_ip_frag/rte_ipv6_reassembly.c | 4 +--
lib/librte_net/rte_ip.h | 27 +++++++++++++++
lib/librte_port/rte_port_ras.c | 6 ++--
9 files changed, 86 insertions(+), 21 deletions(-)
--
2.17.1
next reply other threads:[~2018-10-31 2:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 2:17 Cody Doucette [this message]
2018-10-31 2:17 ` [dpdk-dev] [PATCH v5 1/3] net/failsafe: remove D_XOPEN_SOURCE flag Cody Doucette
2018-10-31 17:02 ` Thomas Monjalon
2018-10-31 21:10 ` Gaëtan Rivet
2018-10-31 2:17 ` [dpdk-dev] [PATCH v5 2/3] net: add IPv6 extension header definitions Cody Doucette
2018-10-31 17:03 ` Thomas Monjalon
2018-11-05 8:45 ` Olivier Matz
2018-10-31 2:17 ` [dpdk-dev] [PATCH v5 3/3] ip_frag: extend IPv6 fragment header retrieval Cody Doucette
2018-10-31 17:03 ` Thomas Monjalon
2018-10-31 19:56 ` Ananyev, Konstantin
2018-11-07 20:21 ` Cody Doucette
2018-11-07 23:00 ` Ananyev, Konstantin
2023-06-12 2:27 ` Stephen Hemminger
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=20181031021758.66752-1-doucette@bu.edu \
--to=doucette@bu.edu \
--cc=dev@dpdk.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).