From: Stephen Hemminger <stephen@networkplumber.org>
To: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Cc: Cody Doucette <doucette@bu.edu>,
"Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>, "Fu, Qiaobin" <qiaobinf@bu.edu>
Subject: Re: [dpdk-dev] [PATCH v5 3/3] ip_frag: extend IPv6 fragment header retrieval
Date: Sun, 11 Jun 2023 19:27:10 -0700 [thread overview]
Message-ID: <20230611192710.5cf09fb0@hermes.local> (raw)
In-Reply-To: <2601191342CEEE43887BDE71AB9772580103069E6F@irsmsx105.ger.corp.intel.com>
On Wed, 7 Nov 2018 23:00:19 +0000
"Ananyev, Konstantin" <konstantin.ananyev@intel.com> wrote:
> >Thanks for reviewing -- I see your point about this patch only removing one of the places where the code makes assumptions about the position of the fragmentation header.
>
> >Unfortunately at the moment I don't have the resources to dedicate to writing the complete solution and doing a performance check, so I think I should withdraw the patch.
>
> Ok, NP that's understandable.
> Again I provided my comments quite late.
Marking this patchset as closed with changes requested.
If someone wants to revive it they can rebase and resubmit.
prev parent reply other threads:[~2023-06-12 2:27 UTC|newest]
Thread overview: 13+ 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
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 [this message]
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=20230611192710.5cf09fb0@hermes.local \
--to=stephen@networkplumber.org \
--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.