[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<171936363254.31895.5945372004965375509.git-patchwork-notify@kernel.org>
Date: Wed, 26 Jun 2024 01:00:32 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Ziwei Xiao <ziweixiao@...gle.com>
Cc: netdev@...r.kernel.org, jeroendb@...gle.com, pkaligineedi@...gle.com,
shailend@...gle.com, davem@...emloft.net, edumazet@...gle.com,
kuba@...nel.org, pabeni@...hat.com, willemb@...gle.com,
hramamurthy@...gle.com, rushilg@...gle.com, horms@...nel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next v3 0/5] gve: Add flow steering support
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@...nel.org>:
On Tue, 25 Jun 2024 00:12:26 +0000 you wrote:
> To support flow steering in GVE driver, there are two adminq changes
> need to be made in advance.
>
> The first one is adding adminq mutex lock, which is to allow the
> incoming flow steering operations to be able to temporarily drop the
> rtnl_lock to reduce the latency for registering flow rules among
> several NICs at the same time. This could be achieved by the future
> changes to reduce the drivers' dependencies on the rtnl lock for
> particular ethtool ops.
>
> [...]
Here is the summary with links:
- [net-next,v3,1/5] gve: Add adminq mutex lock
https://git.kernel.org/netdev/net-next/c/1108566ca509
- [net-next,v3,2/5] gve: Add adminq extended command
https://git.kernel.org/netdev/net-next/c/fcfe6318dbac
- [net-next,v3,3/5] gve: Add flow steering device option
https://git.kernel.org/netdev/net-next/c/3519c00557e0
- [net-next,v3,4/5] gve: Add flow steering adminq commands
https://git.kernel.org/netdev/net-next/c/57718b60df9b
- [net-next,v3,5/5] gve: Add flow steering ethtool support
https://git.kernel.org/netdev/net-next/c/6f3bc487565d
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