[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<175619460575.3698989.15196706539067195769.git-patchwork-notify@kernel.org>
Date: Tue, 26 Aug 2025 07:50:05 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Mingming Cao <mmc@...ux.ibm.com>
Cc: netdev@...r.kernel.org, horms@...nel.org, bjking1@...ux.ibm.com,
haren@...ux.ibm.com, ricklind@...ux.ibm.com, kuba@...nel.org,
edumazet@...gle.com, pabeni@...hat.com, linuxppc-dev@...ts.ozlabs.org,
maddy@...ux.ibm.com, mpe@...erman.id.au
Subject: Re: [PATCH net-next RESEND v4] ibmvnic: Increase max subcrq indirect
entries with fallback
Hello:
This patch was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@...hat.com>:
On Thu, 21 Aug 2025 06:02:15 -0700 you wrote:
> POWER8 support a maximum of 16 subcrq indirect descriptor entries per
> H_SEND_SUB_CRQ_INDIRECT call, while POWER9 and newer hypervisors
> support up to 128 entries. Increasing the max number of indirect
> descriptor entries improves batching efficiency and reduces
> hcall overhead, which enhances throughput under large workload on POWER9+.
>
> Currently, ibmvnic driver always uses a fixed number of max indirect
> descriptor entries (16). send_subcrq_indirect() treats all hypervisor
> errors the same:
> - Cleanup and Drop the entire batch of descriptors.
> - Return an error to the caller.
> - Rely on TCP/IP retransmissions to recover.
> - If the hypervisor returns H_PARAMETER (e.g., because 128
> entries are not supported on POWER8), the driver will continue
> to drop batches, resulting in unnecessary packet loss.
>
> [...]
Here is the summary with links:
- [net-next,RESEND,v4] ibmvnic: Increase max subcrq indirect entries with fallback
https://git.kernel.org/netdev/net-next/c/3c14917953a5
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists