From: patchwork-bot+netdevbpf@kernel.org
To: Wei Fang <wei.fang@nxp.com>
Cc: claudiu.manoil@nxp.com, vladimir.oltean@nxp.com,
xiaoning.wang@nxp.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, Frank.Li@nxp.com, imx@lists.linux.dev,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 net] net: enetc: correct the value of ENETC_RXB_TRUESIZE
Date: Sat, 18 Oct 2025 00:00:12 +0000 [thread overview]
Message-ID: <176074561201.2830883.6352222282006424716.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251016080131.3127122-1-wei.fang@nxp.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 16 Oct 2025 16:01:31 +0800 you wrote:
> The ENETC RX ring uses the page halves flipping mechanism, each page is
> split into two halves for the RX ring to use. And ENETC_RXB_TRUESIZE is
> defined to 2048 to indicate the size of half a page. However, the page
> size is configurable, for ARM64 platform, PAGE_SIZE is default to 4K,
> but it could be configured to 16K or 64K.
>
> When PAGE_SIZE is set to 16K or 64K, ENETC_RXB_TRUESIZE is not correct,
> and the RX ring will always use the first half of the page. This is not
> consistent with the description in the relevant kernel doc and commit
> messages.
>
> [...]
Here is the summary with links:
- [v2,net] net: enetc: correct the value of ENETC_RXB_TRUESIZE
https://git.kernel.org/netdev/net/c/e59bc32df2e9
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-10-18 0:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 8:01 [PATCH v2 net] net: enetc: correct the value of ENETC_RXB_TRUESIZE Wei Fang
2025-10-17 7:22 ` Claudiu Manoil
2025-10-18 0:00 ` patchwork-bot+netdevbpf [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=176074561201.2830883.6352222282006424716.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=andrew+netdev@lunn.ch \
--cc=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=imx@lists.linux.dev \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vladimir.oltean@nxp.com \
--cc=wei.fang@nxp.com \
--cc=xiaoning.wang@nxp.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