DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Feifei Wang <wff_light@vip.163.com>
Cc: dev@dpdk.org, Feifei Wang <wangfeifei40@huawei.com>
Subject: Re: [v4 1/1] net/hinic3: Fix VXLAN TSO issue
Date: Tue, 26 May 2026 06:15:01 -0700	[thread overview]
Message-ID: <20260526061501.697245e4@phoenix.local> (raw)
In-Reply-To: <20260526121820.1093-2-wff_light@vip.163.com>

On Tue, 26 May 2026 20:18:18 +0800
Feifei Wang <wff_light@vip.163.com> wrote:

> From: Feifei Wang <wangfeifei40@huawei.com>
> 
> VXLAN TSO lacks a flag bit, causing the processing function
> to determine that the hardware does not support it, leading
> to improper handling.
> 
> Signed-off-by: Feifei Wang <wangfeifei40@huawei.com>

If this is a bug fix, it needs Fixes: tag and should
have Cc: stable@dpdk.org

> ---
>  drivers/net/hinic3/hinic3_ethdev.c | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/net/hinic3/hinic3_ethdev.c b/drivers/net/hinic3/hinic3_ethdev.c
> index f4eb788..4776bc1 100644
> --- a/drivers/net/hinic3/hinic3_ethdev.c
> +++ b/drivers/net/hinic3/hinic3_ethdev.c
> @@ -652,8 +652,12 @@ hinic3_dev_configure(struct rte_eth_dev *dev)
>  static void
>  hinic3_dev_tnl_tso_support(struct rte_eth_dev_info *info, struct hinic3_nic_dev *nic_dev)
>  {
> +	if (HINIC3_SUPPORT_VXLAN_OFFLOAD(nic_dev))
> +		info->tx_offload_capa |= RTE_ETH_TX_OFFLOAD_VXLAN_TNL_TSO;
> +
>  	if (HINIC3_SUPPORT_GENEVE_OFFLOAD(nic_dev))
>  		info->tx_offload_capa |= RTE_ETH_TX_OFFLOAD_GENEVE_TNL_TSO;
> +
>  	if (HINIC3_SUPPORT_IPXIP_OFFLOAD(nic_dev))
>  		info->tx_offload_capa |= RTE_ETH_TX_OFFLOAD_IPIP_TNL_TSO;
>  }
> @@ -698,7 +702,6 @@ hinic3_dev_infos_get(struct rte_eth_dev *dev, struct rte_eth_dev_info *info)
>  		RTE_ETH_TX_OFFLOAD_SCTP_CKSUM |
>  		RTE_ETH_TX_OFFLOAD_OUTER_IPV4_CKSUM |
>  		RTE_ETH_TX_OFFLOAD_TCP_TSO | RTE_ETH_TX_OFFLOAD_MULTI_SEGS;
> -	if (nic_dev->feature_cap & NIC_F_HTN_CMDQ)
>  		hinic3_dev_tnl_tso_support(info, nic_dev);

If you remove the if here, then you need to fix indentation on
the line below.

  reply	other threads:[~2026-05-26 13:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-20  6:58 [V1 0/1] Add VXLAN TSO function Feifei Wang
2026-05-20  6:58 ` [V1 1/1] net/hinic3: " Feifei Wang
2026-05-20 15:06   ` Stephen Hemminger
2026-05-25  3:30     ` 回复: " wangfeifei (J)
2026-05-23  7:36   ` [V2 0/1] net/hinic3: Fix VXLAN TSO issue Feifei Wang
2026-05-23  7:36     ` [V2 1/1] " Feifei Wang
2026-05-26  3:31   ` [v3 0/1] " Feifei Wang
2026-05-26  3:31     ` [v3 1/1] " Feifei Wang
2026-05-26 12:18   ` [v4 0/1] " Feifei Wang
2026-05-26 12:18     ` [v4 1/1] " Feifei Wang
2026-05-26 13:15       ` Stephen Hemminger [this message]
2026-05-28 10:58       ` [v5 " Feifei Wang
2026-05-28 13:01       ` [v6 0/2] net/hinic3: Fix the hinic3 driver issue Feifei Wang
2026-05-28 13:01         ` [v6 1/2] net/hinic3: Fix VXLAN TSO issue Feifei Wang
2026-05-28 13:01         ` [v6 2/2] net/hinic3: Modify SP230 VF device id Feifei Wang
2026-05-28 21:00         ` [v6 0/2] net/hinic3: Fix the hinic3 driver issue Stephen Hemminger

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=20260526061501.697245e4@phoenix.local \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=wangfeifei40@huawei.com \
    --cc=wff_light@vip.163.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