From: Ivan Malov <ivan.malov@arknetworks.am>
To: Huisong Li <lihuisong@huawei.com>
Cc: dev@dpdk.org, ferruh.yigit@amd.com,
Aman Singh <aman.deep.singh@intel.com>,
Yuying Zhang <yuying.zhang@intel.com>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Bernard Iremonger <bernard.iremonger@intel.com>,
Ivan Ilchenko <ivan.ilchenko@oktetlabs.ru>,
liuyonglong@huawei.com
Subject: Re: [PATCH v1 1/3] app/testpmd: fix random value to set tunnel TSO
Date: Fri, 10 Nov 2023 15:42:07 +0400 (+04) [thread overview]
Message-ID: <7046579c-a129-69c2-f72b-94ab2fa5d5fd@arknetworks.am> (raw)
In-Reply-To: <20231110081925.14142-2-lihuisong@huawei.com>
Hi,
(minor question below)
On Fri, 10 Nov 2023, Huisong Li wrote:
> Currently, testpmd set tunnel TSO offload even if fail to get dev_info.
> In this case, the 'tx_offload_capa' in dev_info is a random value,
>
> Fixes: 6f51deb903b2 ("app/testpmd: check status of getting ethdev info")
> Cc: stable@dpdk.org
>
> Signed-off-by: Huisong Li <lihuisong@huawei.com>
> ---
> app/test-pmd/cmdline.c | 29 ++++++++++++++---------------
> 1 file changed, 14 insertions(+), 15 deletions(-)
>
> diff --git a/app/test-pmd/cmdline.c b/app/test-pmd/cmdline.c
> index 05078f8377..25462bdbfc 100644
> --- a/app/test-pmd/cmdline.c
> +++ b/app/test-pmd/cmdline.c
> @@ -5035,39 +5035,33 @@ struct cmd_tunnel_tso_set_result {
> portid_t port_id;
> };
>
> -static struct rte_eth_dev_info
> -check_tunnel_tso_nic_support(portid_t port_id)
> +static void
> +check_tunnel_tso_nic_support(portid_t port_id, uint64_t tx_offload_capa)
> {
> - struct rte_eth_dev_info dev_info;
Why not just initialise this to zeros?
> -
> - if (eth_dev_info_get_print_err(port_id, &dev_info) != 0)
> - return dev_info;
> -
> - if (!(dev_info.tx_offload_capa & RTE_ETH_TX_OFFLOAD_VXLAN_TNL_TSO))
> + if (!(tx_offload_capa & RTE_ETH_TX_OFFLOAD_VXLAN_TNL_TSO))
> fprintf(stderr,
> "Warning: VXLAN TUNNEL TSO not supported therefore not enabled for port %d\n",
> port_id);
> - if (!(dev_info.tx_offload_capa & RTE_ETH_TX_OFFLOAD_GRE_TNL_TSO))
> + if (!(tx_offload_capa & RTE_ETH_TX_OFFLOAD_GRE_TNL_TSO))
> fprintf(stderr,
> "Warning: GRE TUNNEL TSO not supported therefore not enabled for port %d\n",
> port_id);
> - if (!(dev_info.tx_offload_capa & RTE_ETH_TX_OFFLOAD_IPIP_TNL_TSO))
> + if (!(tx_offload_capa & RTE_ETH_TX_OFFLOAD_IPIP_TNL_TSO))
> fprintf(stderr,
> "Warning: IPIP TUNNEL TSO not supported therefore not enabled for port %d\n",
> port_id);
> - if (!(dev_info.tx_offload_capa & RTE_ETH_TX_OFFLOAD_GENEVE_TNL_TSO))
> + if (!(tx_offload_capa & RTE_ETH_TX_OFFLOAD_GENEVE_TNL_TSO))
> fprintf(stderr,
> "Warning: GENEVE TUNNEL TSO not supported therefore not enabled for port %d\n",
> port_id);
> - if (!(dev_info.tx_offload_capa & RTE_ETH_TX_OFFLOAD_IP_TNL_TSO))
> + if (!(tx_offload_capa & RTE_ETH_TX_OFFLOAD_IP_TNL_TSO))
> fprintf(stderr,
> "Warning: IP TUNNEL TSO not supported therefore not enabled for port %d\n",
> port_id);
> - if (!(dev_info.tx_offload_capa & RTE_ETH_TX_OFFLOAD_UDP_TNL_TSO))
> + if (!(tx_offload_capa & RTE_ETH_TX_OFFLOAD_UDP_TNL_TSO))
> fprintf(stderr,
> "Warning: UDP TUNNEL TSO not supported therefore not enabled for port %d\n",
> port_id);
> - return dev_info;
> }
>
> static void
> @@ -5077,6 +5071,7 @@ cmd_tunnel_tso_set_parsed(void *parsed_result,
> {
> struct cmd_tunnel_tso_set_result *res = parsed_result;
> struct rte_eth_dev_info dev_info;
> + int ret;
>
> if (port_id_is_invalid(res->port_id, ENABLED_WARN))
> return;
> @@ -5088,7 +5083,11 @@ cmd_tunnel_tso_set_parsed(void *parsed_result,
> if (!strcmp(res->mode, "set"))
> ports[res->port_id].tunnel_tso_segsz = res->tso_segsz;
>
> - dev_info = check_tunnel_tso_nic_support(res->port_id);
> + ret = eth_dev_info_get_print_err(res->port_id, &dev_info);
> + if (ret != 0)
> + return;
> +
> + check_tunnel_tso_nic_support(res->port_id, dev_info.tx_offload_capa);
> if (ports[res->port_id].tunnel_tso_segsz == 0) {
> ports[res->port_id].dev_conf.txmode.offloads &=
> ~(RTE_ETH_TX_OFFLOAD_VXLAN_TNL_TSO |
> --
> 2.33.0
>
>
Thank you.
next prev parent reply other threads:[~2023-11-10 11:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-10 8:19 [PATCH v1 0/3] app/testpmd: fix the command " Huisong Li
2023-11-10 8:19 ` [PATCH v1 1/3] app/testpmd: fix random value " Huisong Li
2023-11-10 11:42 ` Ivan Malov [this message]
2023-11-11 1:17 ` lihuisong (C)
2023-11-11 3:22 ` Ferruh Yigit
2023-11-10 8:19 ` [PATCH v1 2/3] app/testpmd: add the explicit check for tunnel TSO offload Huisong Li
2023-11-11 3:30 ` Ferruh Yigit
2023-11-11 4:27 ` lihuisong (C)
2023-11-10 8:19 ` [PATCH v1 3/3] app/testpmd: fix unnecessary change when set tunnel TSO Huisong Li
2023-11-11 3:37 ` Ferruh Yigit
2023-11-11 4:28 ` lihuisong (C)
2023-11-11 4:59 ` [PATCH v2 0/3] app/testpmd: fix the command to " Huisong Li
2023-11-11 4:59 ` [PATCH v2 1/3] app/testpmd: fix random value " Huisong Li
2023-11-11 4:59 ` [PATCH v2 2/3] app/testpmd: add the explicit check for tunnel TSO offload Huisong Li
2023-11-11 4:59 ` [PATCH v2 3/3] app/testpmd: fix unnecessary change when set tunnel TSO Huisong Li
2023-11-11 5:59 ` [PATCH v2 0/3] app/testpmd: fix the command to " Ferruh Yigit
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=7046579c-a129-69c2-f72b-94ab2fa5d5fd@arknetworks.am \
--to=ivan.malov@arknetworks.am \
--cc=aman.deep.singh@intel.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=ivan.ilchenko@oktetlabs.ru \
--cc=lihuisong@huawei.com \
--cc=liuyonglong@huawei.com \
--cc=yuying.zhang@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).