From: Thomas Monjalon <thomas@monjalon.net>
To: Konstantin Ananyev <konstantin.ananyev@intel.com>
Cc: dev@dpdk.org, Cody Doucette <doucette@bu.edu>,
Cristian Dumitrescu <cristian.dumitrescu@intel.com>,
Qiaobin Fu <qiaobinf@bu.edu>
Subject: Re: [PATCH v5 3/3] ip_frag: extend IPv6 fragment header retrieval
Date: Wed, 31 Oct 2018 18:03:15 +0100 [thread overview]
Message-ID: <1693070.K3n6qVy3Rk@xps> (raw)
In-Reply-To: <20181031021758.66752-4-doucette@bu.edu>
31/10/2018 03:17, Cody Doucette:
> Add the ability to parse IPv6 extenders to find the
> IPv6 fragment header, and update callers.
>
> According to RFC 8200, there is no guarantee that the IPv6
> Fragment extension header will come before any other extension
> header, even though it is recommended.
>
> Signed-off-by: Cody Doucette <doucette@bu.edu>
> Signed-off-by: Qiaobin Fu <qiaobinf@bu.edu>
> Reviewed-by: Michel Machado <michel@digirati.com.br>
Konstantin, did you already ack this patch?
next prev parent reply other threads:[~2018-10-31 17:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 2:17 [PATCH v5 0/3] Extend rte_ipv6_frag_get_ipv6_fragment_header() Cody Doucette
2018-10-31 2:17 ` [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 ` [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 ` [PATCH v5 3/3] ip_frag: extend IPv6 fragment header retrieval Cody Doucette
2018-10-31 17:03 ` Thomas Monjalon [this message]
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 ` [dpdk-dev] " Stephen Hemminger
-- strict thread matches above, loose matches on Subject: below --
2018-10-31 0:17 [PATCH v4 0/3] Extend rte_ipv6_frag_get_ipv6_fragment_header() Cody Doucette
2018-10-31 0:17 ` [PATCH v5 3/3] ip_frag: extend IPv6 fragment header retrieval Cody Doucette
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=1693070.K3n6qVy3Rk@xps \
--to=thomas@monjalon.net \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=doucette@bu.edu \
--cc=konstantin.ananyev@intel.com \
--cc=qiaobinf@bu.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.