[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<173995863100.531989.91959446814814394.git-patchwork-notify@kernel.org>
Date: Wed, 19 Feb 2025 09:50:31 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Shradha Gupta <shradhagupta@...ux.microsoft.com>
Cc: linux-hyperv@...r.kernel.org, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, kys@...rosoft.com, haiyangz@...rosoft.com,
wei.liu@...nel.org, decui@...rosoft.com, andrew+netdev@...n.ch,
davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com,
longli@...rosoft.com, kotaranov@...rosoft.com,
schakrabarti@...ux.microsoft.com, erick.archer@...look.com,
shradhagupta@...rosoft.com
Subject: Re: [PATCH v3 net-next 0/2] Enable Big TCP for MANA devices
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@...emloft.net>:
On Sun, 16 Feb 2025 19:41:55 -0800 you wrote:
> Allow the max gso/gro aggregated pkt size to go up to GSO_MAX_SIZE for
> MANA NIC. On Azure, this not possible without allowing the same for
> netvsc NIC (as the NICs are bonded together).
> Therefore, we use netif_set_tso_max_size() to set max aggregated pkt
> size
> to VF's tso_max_size for netvsc too, when the data path is switched over
> to the VF
>
> [...]
Here is the summary with links:
- [v3,net-next,1/2] net: mana: Allow tso_max_size to go up-to GSO_MAX_SIZE
https://git.kernel.org/netdev/net-next/c/27315836f4bc
- [v3,net-next,2/2] hv_netvsc: Use VF's tso_max_size value when data path is VF
https://git.kernel.org/netdev/net-next/c/685920920e3d
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