[net-next,v3,0/5] gve: Add flow steering support

Message

Ziwei Xiao June 25, 2024, 12:12 a.m. UTC

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.

The second one is to add the extended adminq command so that we can
support larger adminq command such as configure_flow_rule command. In
that patch, there is a new added function called
gve_adminq_execute_extended_cmd with the attribute of __maybe_unused.
That attribute will be removed in the third patch of this series where
it will use the previously unused function.

And the other three patches are needed for the actual flow steering
feature support in driver.

Jeroen de Borst (4):
  gve: Add adminq extended command
  gve: Add flow steering device option
  gve: Add flow steering adminq commands
  gve: Add flow steering ethtool support

Ziwei Xiao (1):
  gve: Add adminq mutex lock

 drivers/net/ethernet/google/gve/Makefile      |   2 +-
 drivers/net/ethernet/google/gve/gve.h         |  54 +++-
 drivers/net/ethernet/google/gve/gve_adminq.c  | 228 +++++++++++++-
 drivers/net/ethernet/google/gve/gve_adminq.h  | 103 ++++++
 drivers/net/ethernet/google/gve/gve_ethtool.c |  72 ++++-
 .../net/ethernet/google/gve/gve_flow_rule.c   | 298 ++++++++++++++++++
 drivers/net/ethernet/google/gve/gve_main.c    |  83 ++++-
 7 files changed, 817 insertions(+), 23 deletions(-)
 create mode 100644 drivers/net/ethernet/google/gve/gve_flow_rule.c

Comments

[e-mail] June 26, 2024, 1 a.m. UTC | #1

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <[e-mail]>:

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!