From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
Ivan Malov <ivan.malov@oktetlabs.ru>,
Olivier Matz <olivier.matz@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Kulasek, TomaszX" <tomaszx.kulasek@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] net: fix encapsulation markers for inner L3 offset
Date: Thu, 27 Jun 2019 16:32:15 +0100 [thread overview]
Message-ID: <27212527-f987-a037-8f91-2ee015d3361f@intel.com> (raw)
In-Reply-To: <2601191342CEEE43887BDE71AB97725801689E3F0D@IRSMSX104.ger.corp.intel.com>
On 6/24/2019 12:35 PM, Ananyev, Konstantin wrote:
>
>
>> -----Original Message-----
>> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Ivan Malov
>> Sent: Friday, May 24, 2019 3:57 PM
>> To: Olivier Matz <olivier.matz@6wind.com>
>> Cc: dev@dpdk.org; Kulasek, TomaszX <tomaszx.kulasek@intel.com>; stable@dpdk.org
>> Subject: [dpdk-dev] [PATCH] net: fix encapsulation markers for inner L3 offset
>>
>> The API to prepare checksum offloads employs outer
>> IP checksum flag to tell regular IPv4 packets from
>> tunnel packets with outer IPv4 encapsulation. This
>> flag cannot serve as a marker for the said purpose
>> because a packet can have outer IPv4 encapsulation
>> and may not have outer IP checksum offload request.
>>
>> Fix the API by changing the said criterion to test
>> outer IPv4 flag rather than outer IP checksum flag.
>> Use simpler spelling of the conditional expression.
>>
>> Fixes: 4fb7e803eb1a ("ethdev: add Tx preparation")
>> Cc: Tomasz Kulasek <tomaszx.kulasek@intel.com>
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Ivan Malov <ivan.malov@oktetlabs.ru>
>> Reviewed-by: Andrew Rybchenko <arybchenko@solarflare.com>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2019-06-27 15:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-24 14:57 [dpdk-stable] " Ivan Malov
2019-06-24 11:35 ` [dpdk-stable] [dpdk-dev] " Ananyev, Konstantin
2019-06-27 15:32 ` Ferruh Yigit [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=27212527-f987-a037-8f91-2ee015d3361f@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=ivan.malov@oktetlabs.ru \
--cc=konstantin.ananyev@intel.com \
--cc=olivier.matz@6wind.com \
--cc=stable@dpdk.org \
--cc=tomaszx.kulasek@intel.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).