From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Chaoyong He <chaoyong.he@corigine.com>, dev@dpdk.org
Cc: oss-drivers@corigine.com, niklas.soderlund@corigine.com,
Peng Zhang <peng.zhang@corigine.com>,
stable@dpdk.org
Subject: Re: [PATCH] net/nfp: set the appropriate initialized value of flbufsz
Date: Thu, 13 Oct 2022 13:00:10 +0100 [thread overview]
Message-ID: <482436be-c20f-09a0-d4e7-b46458026317@amd.com> (raw)
In-Reply-To: <1665384495-24990-1-git-send-email-chaoyong.he@corigine.com>
On 10/10/2022 7:48 AM, Chaoyong He wrote:
> From: Peng Zhang <peng.zhang@corigine.com>
>
> When the testpmd app start-up with parameter max-pkt-len, it will set MTU.
> But the initialized value of flubfsz is inappropriate, if the value of
> flbufsz is smaller than the valude of max-pkt-len, the testpmd app will
> start fail.
>
What is the failure in the testpmd?
This patch is fixing something but it is not clear what is fixed, the
concern is it may be changing driver to make something pass in test
application (testpmd).
What is 'flubfsz', is it Hw configured frame buffer size?
> Fixes: 5c305e218f15 ("net/nfp: fix initialization")
> Cc: stable@dpdk.org
>
> Signed-off-by: Peng Zhang <peng.zhang@corigine.com>
> Reviewed-by: Chaoyong He <chaoyong.he@corigine.com>
> Reviewed-by: Niklas Söderlund <niklas.soderlund@corigine.com>
> ---
> drivers/net/nfp/nfp_ethdev.c | 2 +-
> drivers/net/nfp/nfp_ethdev_vf.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/nfp/nfp_ethdev.c b/drivers/net/nfp/nfp_ethdev.c
> index 5cdd34e588..b95e623f1f 100644
> --- a/drivers/net/nfp/nfp_ethdev.c
> +++ b/drivers/net/nfp/nfp_ethdev.c
> @@ -517,7 +517,7 @@ nfp_net_init(struct rte_eth_dev *eth_dev)
> hw->cap = nn_cfg_readl(hw, NFP_NET_CFG_CAP);
> hw->max_mtu = nn_cfg_readl(hw, NFP_NET_CFG_MAX_MTU);
> hw->mtu = RTE_ETHER_MTU;
> - hw->flbufsz = RTE_ETHER_MTU;
> + hw->flbufsz = hw->max_mtu;
>
> /* VLAN insertion is incompatible with LSOv2 */
> if (hw->cap & NFP_NET_CFG_CTRL_LSO2)
> diff --git a/drivers/net/nfp/nfp_ethdev_vf.c b/drivers/net/nfp/nfp_ethdev_vf.c
> index d304d78d34..47acb4c60e 100644
> --- a/drivers/net/nfp/nfp_ethdev_vf.c
> +++ b/drivers/net/nfp/nfp_ethdev_vf.c
> @@ -396,7 +396,7 @@ nfp_netvf_init(struct rte_eth_dev *eth_dev)
> hw->cap = nn_cfg_readl(hw, NFP_NET_CFG_CAP);
> hw->max_mtu = nn_cfg_readl(hw, NFP_NET_CFG_MAX_MTU);
> hw->mtu = RTE_ETHER_MTU;
> - hw->flbufsz = RTE_ETHER_MTU;
> + hw->flbufsz = hw->max_mtu;
>
> /* VLAN insertion is incompatible with LSOv2 */
> if (hw->cap & NFP_NET_CFG_CTRL_LSO2)
next prev parent reply other threads:[~2022-10-13 12:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-10 6:48 Chaoyong He
2022-10-13 12:00 ` Ferruh Yigit [this message]
2022-10-15 7:38 ` Nole Zhang
2022-10-17 12:11 ` Ferruh Yigit
2022-10-18 1:41 ` Nole Zhang
2022-10-18 7:51 ` Ferruh Yigit
2022-10-18 8:51 ` Nole Zhang
2022-10-18 9:36 ` Ferruh Yigit
2022-10-18 9:50 ` Nole Zhang
2022-10-18 10:42 ` Ferruh Yigit
2022-10-21 6:27 ` [PATCH v2] net/nfp: ensure the MTU can work Chaoyong He
2022-10-21 9:59 ` 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=482436be-c20f-09a0-d4e7-b46458026317@amd.com \
--to=ferruh.yigit@amd.com \
--cc=chaoyong.he@corigine.com \
--cc=dev@dpdk.org \
--cc=niklas.soderlund@corigine.com \
--cc=oss-drivers@corigine.com \
--cc=peng.zhang@corigine.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).