From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Chaoyong He <chaoyong.he@corigine.com>, dev@dpdk.org
Cc: oss-drivers@corigine.com, Long Wu <long.wu@corigine.com>
Subject: Re: [PATCH] net/nfp: modify Rx buffer size setting logic
Date: Thu, 17 Oct 2024 01:53:25 +0100 [thread overview]
Message-ID: <6e8dc9c4-f8f9-4914-b2c1-27024a5b2c18@amd.com> (raw)
In-Reply-To: <20241016081522.4005003-1-chaoyong.he@corigine.com>
On 10/16/2024 9:15 AM, Chaoyong He wrote:
> From: Long Wu <long.wu@corigine.com>
>
> In the previous logic, NFP driver would modify hardware Rx buffer size
> every time rxq was set. This will cause the setting of one Rx queue
> to affect all Rx queues, resulting in the card being unable to receive
> packets properly in some cases.
>
> Modify this logic so that after the first initialization, only when
> the Rx queue buffer size is greater than the current hardware set size
> will it be modified.
>
> Signed-off-by: Long Wu <long.wu@corigine.com>
> Reviewed-by: Chaoyong He <chaoyong.he@corigine.com>
>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2024-10-17 0:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 8:15 Chaoyong He
2024-10-17 0:53 ` 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=6e8dc9c4-f8f9-4914-b2c1-27024a5b2c18@amd.com \
--to=ferruh.yigit@amd.com \
--cc=chaoyong.he@corigine.com \
--cc=dev@dpdk.org \
--cc=long.wu@corigine.com \
--cc=oss-drivers@corigine.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).