DPDK patches and discussions
 help / color / mirror / Atom feed
From: Raslan Darawsheh <rasland@mellanox.com>
To: Slava Ovsiienko <viacheslavo@mellanox.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: Eli Britstein <elibr@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH v2] net/mlx5: zero out UDP csum for IPv6 encap headers
Date: Mon, 8 Jul 2019 11:40:22 +0000	[thread overview]
Message-ID: <DB3PR0502MB39644C0586803624E220A0ACC2F60@DB3PR0502MB3964.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <1562238988-13138-1-git-send-email-viacheslavo@mellanox.com>

Hi,

> -----Original Message-----
> From: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
> Sent: Thursday, July 4, 2019 2:16 PM
> To: dev@dpdk.org
> Cc: Raslan Darawsheh <rasland@mellanox.com>; Eli Britstein
> <elibr@mellanox.com>
> Subject: [PATCH v2] net/mlx5: zero out UDP csum for IPv6 encap headers
> 
> From: Eli Britstein <elibr@mellanox.com>
> 
> Mellanox NICs do not support UDP checksum hardware tx offload over IPv6.
> This limitation becomes critical for UDP based tunnels like VXLAN.
> Beside the UDP checksum validity is required by IPv6 there is an option
> in Linux to allow accepting UDP zero sum (see udp6zerocsumrx in iproute2
> package).
> 
> This patch zeroes out the UDP checksum field for encapsulation headers
> in raw encap action.
> 
> Signed-off-by: Eli Britstein <elibr@mellanox.com>
> Acked-by: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
> ---
>  drivers/net/mlx5/mlx5_flow_dv.c | 46
> +++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 46 insertions(+)
> 

Patch applied to next-net-mlx,

Kindest regards,
Raslan Darawsheh

      reply	other threads:[~2019-07-08 11:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-04 11:16 Viacheslav Ovsiienko
2019-07-08 11:40 ` Raslan Darawsheh [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=DB3PR0502MB39644C0586803624E220A0ACC2F60@DB3PR0502MB3964.eurprd05.prod.outlook.com \
    --to=rasland@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=elibr@mellanox.com \
    --cc=viacheslavo@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).