patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: Kalesh A P <kalesh-anakkur.purayil@broadcom.com>, stable@dpdk.org
Subject: Re: [PATCH 21.11] net/bnxt: fix tunnel stateless offloads
Date: Thu, 23 Jun 2022 14:58:55 +0100	[thread overview]
Message-ID: <7a0ca50d-7ead-2c84-5499-029d680de323@redhat.com> (raw)
In-Reply-To: <20220622083713.23976-1-kalesh-anakkur.purayil@broadcom.com>

On 22/06/2022 09:37, Kalesh A P wrote:
> From: Kalesh AP<kalesh-anakkur.purayil@broadcom.com>
> 
> [ upstream commit c0278f6e52399f7612f9f1a9d52434071ac49921 ]
> 
> The HW only supports tunnel header parsing globally for supported tunnel
> types. When a function uses one default VNIC to receive both the tunnel
> and non-tunnel packets, applying the same stateless offload operation to
> both tunnel and non-tunnel packets can cause problems in certain scenarios.
> To workaround these problems, the firmware advertises no tunnel header
> parsing capabilities to the driver using the HWRM_FUNC_QCAPS.
> The driver must check this flag setting and accordingly not advertise
> tunnel packet stateless offload capabilities to the stack.
> 
> If the device supports VXLAN, GRE, IPIP and GENEVE tunnel parsing,
> then reports RX_OFFLOAD_OUTER_IPV4_CKSUM, RX_OFFLOAD_OUTER_UDP_CKSUM
> and TX_OFFLOAD_OUTER_IPV4_CKSUM in the Rx/Tx offload capabilities of
> the device.
> Also, advertise tunnel TSO capabilities based on FW support.
> 
> Backported the needed changes from "2646926002d8" to fix build failures.
> 
> Fixes: 0a6d2a720078 ("net/bnxt: get device infos")
> 
> Signed-off-by: Kalesh AP<kalesh-anakkur.purayil@broadcom.com>
> Reviewed-by: Ajit Khaparde<ajit.khaparde@broadcom.com>
> Reviewed-by: Somnath Kotur<somnath.kotur@broadcom.com>

Thanks, applied.


      reply	other threads:[~2022-06-23 13:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-22  8:37 Kalesh A P
2022-06-23 13:58 ` Kevin Traynor [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=7a0ca50d-7ead-2c84-5499-029d680de323@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=kalesh-anakkur.purayil@broadcom.com \
    --cc=stable@dpdk.org \
    /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).