From: Ferruh Yigit <ferruh.yigit@xilinx.com>
To: Peng Zhang <peng.zhang@corigine.com>,
Chaoyong He <chaoyong.he@corigine.com>
Cc: <niklas.soderlund@corigine.com>, <stable@dpdk.org>, <dev@dpdk.org>
Subject: Re: [PATCH v2] net/nfp: initialize the flbufsz
Date: Fri, 17 Jun 2022 16:31:40 +0100 [thread overview]
Message-ID: <ce1a300b-6c8b-19e4-de4b-ce6e4aefbc6c@xilinx.com> (raw)
In-Reply-To: <20220615101417.3139606-1-peng.zhang@corigine.com>
On 6/15/2022 11:14 AM, Peng Zhang wrote:
> When the testpmd start-up, it will check MTU range,
> if MTU > flubfsz, it will lead testpmd start fail.
> Because the hw->flbufsz doesn't have the initialized
> value, so it will lead the bug.
>
> Fixes: 97a30c4d4c7b ("net/nfp: make sure MTU is never larger than mbuf size")
> Cc:stable@dpdk.org
>
> Signed-off-by: Peng Zhang<peng.zhang@corigine.com>
> Signed-off-by: Chaoyong He<chaoyong.he@corigine.com>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2022-06-17 15:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 14:47 [PATCH] " Peng Zhang
2022-06-15 10:14 ` [PATCH v2] " Peng Zhang
2022-06-17 15:31 ` Ferruh Yigit [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=ce1a300b-6c8b-19e4-de4b-ce6e4aefbc6c@xilinx.com \
--to=ferruh.yigit@xilinx.com \
--cc=chaoyong.he@corigine.com \
--cc=dev@dpdk.org \
--cc=niklas.soderlund@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).