From: patchwork-bot+netdevbpf@kernel.org
To: Ziwei Xiao <ziweixiao@google.com>
Cc: netdev@vger.kernel.org, jeroendb@google.com,
pkaligineedi@google.com, shailend@google.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, willemb@google.com, hramamurthy@google.com,
rushilg@google.com, horms@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v3 0/5] gve: Add flow steering support
Date: Wed, 26 Jun 2024 01:00:32 +0000 [thread overview]
Message-ID: <171936363254.31895.5945372004965375509.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240625001232.1476315-1-ziweixiao@google.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.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
prev parent reply other threads:[~2024-06-26 1:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-25 0:12 [PATCH net-next v3 0/5] gve: Add flow steering support Ziwei Xiao
2024-06-25 0:12 ` [PATCH net-next v3 1/5] gve: Add adminq mutex lock Ziwei Xiao
2024-06-25 0:12 ` [PATCH net-next v3 2/5] gve: Add adminq extended command Ziwei Xiao
2024-06-25 0:12 ` [PATCH net-next v3 3/5] gve: Add flow steering device option Ziwei Xiao
2024-06-25 0:12 ` [PATCH net-next v3 4/5] gve: Add flow steering adminq commands Ziwei Xiao
2024-06-25 0:12 ` [PATCH net-next v3 5/5] gve: Add flow steering ethtool support Ziwei Xiao
2024-06-26 1: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=171936363254.31895.5945372004965375509.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=hramamurthy@google.com \
--cc=jeroendb@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pkaligineedi@google.com \
--cc=rushilg@google.com \
--cc=shailend@google.com \
--cc=willemb@google.com \
--cc=ziweixiao@google.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