From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Nélio Laranjeiro" <nelio.laranjeiro@6wind.com>,
"Shahaf Shuler" <shahafs@mellanox.com>
Cc: adrien.mazarguil@6wind.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2 1/2] net/mlx5: add hardware checksum offload for tunnel packets
Date: Mon, 6 Mar 2017 09:35:04 +0000 [thread overview]
Message-ID: <9ae9947c-7473-e86f-995f-4ace0c0792c5@intel.com> (raw)
In-Reply-To: <20170302091724.GE22756@autoinstall.dev.6wind.com>
On 3/2/2017 9:17 AM, Nélio Laranjeiro wrote:
> On Thu, Mar 02, 2017 at 11:05:44AM +0200, Shahaf Shuler wrote:
>> Prior to this commit Tx checksum offload was supported only for the
>> inner headers.
>> This commit adds support for the hardware to compute the checksum for the
>> outer headers as well.
>>
>> The support is for tunneling protocols GRE and VXLAN.
>>
>> Signed-off-by: Shahaf Shuler <shahafs@mellanox.com>
> Acked-by: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2017-03-06 9:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 15:53 [dpdk-dev] [PATCH 0/2] net/mlx5: add Tx offloads for tunneled packets Shahaf Shuler
2017-02-28 15:53 ` [dpdk-dev] [PATCH 1/2] net/mlx5: add hardware checksum offload for tunnel packets Shahaf Shuler
2017-03-01 14:47 ` Nélio Laranjeiro
2017-02-28 15:53 ` [dpdk-dev] [PATCH 2/2] net/mlx5: add hardware TSO support for VXLAN and GRE Shahaf Shuler
2017-03-01 14:51 ` Nélio Laranjeiro
2017-03-01 9:23 ` [dpdk-dev] [PATCH 0/2] net/mlx5: add Tx offloads for tunneled packets Shahaf Shuler
2017-03-01 11:26 ` Shahaf Shuler
2017-03-02 9:05 ` [dpdk-dev] [PATCH v2 1/2] net/mlx5: add hardware checksum offload for tunnel packets Shahaf Shuler
2017-03-02 9:05 ` [dpdk-dev] [PATCH v2 2/2] net/mlx5: add hardware TSO support for VXLAN and GRE Shahaf Shuler
2017-03-02 9:17 ` [dpdk-dev] [PATCH v2 1/2] net/mlx5: add hardware checksum offload for tunnel packets Nélio Laranjeiro
2017-03-06 9:35 ` 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=9ae9947c-7473-e86f-995f-4ace0c0792c5@intel.com \
--to=ferruh.yigit@intel.com \
--cc=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=nelio.laranjeiro@6wind.com \
--cc=shahafs@mellanox.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).