From: Owen Hilyard <ohilyard@iol.unh.edu>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, dts@dpdk.org, ferruh.yigit@intel.com,
arybchenko@solarflare.com, Olivier Matz <olivier.matz@6wind.com>,
david.marchand@redhat.com, ivan.malov@oktetlabs.ru,
bruce.richardson@intel.com, jerin.jacob@caviumnetworks.com,
Lincoln Lavoie <lylavoie@iol.unh.edu>,
rasland@mellanox.com, j.hendergart@f5.com
Subject: Re: [dpdk-dev] Hardware Checksum Checks Offload Feature
Date: Mon, 29 Jun 2020 10:01:34 -0400 [thread overview]
Message-ID: <CAHx6DYAU1y-ni1Qrf2QE3urcuiGQt5kA-qdQbTCLcSUYDG-pTA@mail.gmail.com> (raw)
In-Reply-To: <CAHx6DYCyDxiSUE1b9cnF9jZ9AT6dRffCCke+CrqU-72jGFvfqw@mail.gmail.com>
It seems that GENEVE is not supported in the version of scapy that is
currently used. It is supported in the next version. I didn't want to make
the decision to either force an update, spend time attempting to backport
the protocol and then adding a way to automatically add that patch onto an
existing version, or drop the protocol from the test matrix without
community input.
Thoughts?
On Thu, Jun 25, 2020 at 11:54 AM Owen Hilyard <ohilyard@iol.unh.edu> wrote:
> I can do that.
>
> Thanks for the clarification
>
> On Thu, Jun 25, 2020 at 11:25 AM Thomas Monjalon <thomas@monjalon.net>
> wrote:
>
>> > > I think you should describe all the protocols you want to test.
>> >
>> > Could you please elaborate on this?
>>
>> I mean doing a test matrix inluding IP, TCP, UDP, VXLAN, GENEVE, etc.
>>
>>
>>
next prev parent reply other threads:[~2020-06-29 14:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-24 15:14 Owen Hilyard
2020-06-24 20:20 ` Thomas Monjalon
2020-06-25 14:51 ` Owen Hilyard
2020-06-25 15:25 ` Thomas Monjalon
2020-06-25 15:54 ` Owen Hilyard
2020-06-29 14:01 ` Owen Hilyard [this message]
2020-06-29 14:41 ` Thomas Monjalon
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=CAHx6DYAU1y-ni1Qrf2QE3urcuiGQt5kA-qdQbTCLcSUYDG-pTA@mail.gmail.com \
--to=ohilyard@iol.unh.edu \
--cc=arybchenko@solarflare.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=dts@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=ivan.malov@oktetlabs.ru \
--cc=j.hendergart@f5.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=lylavoie@iol.unh.edu \
--cc=olivier.matz@6wind.com \
--cc=rasland@mellanox.com \
--cc=thomas@monjalon.net \
/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).