From: Subbaraya Sundeep <sbhatta@marvell.com>
To: Breno Leitao <leitao@debian.org>
Cc: Joshua Washington <joshwash@google.com>,
Harshitha Ramamurthy <hramamurthy@google.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next] net: gve: convert to use .get_rx_ring_count
Date: Tue, 23 Dec 2025 09:51:19 +0530 [thread overview]
Message-ID: <20251223042119.GA319551@kernel-ep2> (raw)
In-Reply-To: <20251222-gxring_google-v1-1-35e7467e5c1a@debian.org>
On 2025-12-22 at 22:46:27, Breno Leitao (leitao@debian.org) wrote:
> Convert the Google Virtual Ethernet (GVE) driver to use the new
> .get_rx_ring_count ethtool operation instead of handling
> ETHTOOL_GRXRINGS in .get_rxnfc. This simplifies the code by moving the
> ring count query to a dedicated callback.
>
> The new callback provides the same functionality in a more direct way,
> following the ongoing ethtool API modernization.
>
> Signed-off-by: Breno Leitao <leitao@debian.org>
Reviewed-by: Subbaraya Sundeep <sbhatta@marvell.com>
Please repost after net-next is open.
Thanks,
Sundeep
> ---
> PS: This was compile-tested only.
> ---
> drivers/net/ethernet/google/gve/gve_ethtool.c | 11 ++++++++---
> 1 file changed, 8 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/net/ethernet/google/gve/gve_ethtool.c b/drivers/net/ethernet/google/gve/gve_ethtool.c
> index 52500ae8348e..9ed1d4529427 100644
> --- a/drivers/net/ethernet/google/gve/gve_ethtool.c
> +++ b/drivers/net/ethernet/google/gve/gve_ethtool.c
> @@ -815,15 +815,19 @@ static int gve_set_rxnfc(struct net_device *netdev, struct ethtool_rxnfc *cmd)
> return err;
> }
>
> +static u32 gve_get_rx_ring_count(struct net_device *netdev)
> +{
> + struct gve_priv *priv = netdev_priv(netdev);
> +
> + return priv->rx_cfg.num_queues;
> +}
> +
> static int gve_get_rxnfc(struct net_device *netdev, struct ethtool_rxnfc *cmd, u32 *rule_locs)
> {
> struct gve_priv *priv = netdev_priv(netdev);
> int err = 0;
>
> switch (cmd->cmd) {
> - case ETHTOOL_GRXRINGS:
> - cmd->data = priv->rx_cfg.num_queues;
> - break;
> case ETHTOOL_GRXCLSRLCNT:
> if (!priv->max_flow_rules)
> return -EOPNOTSUPP;
> @@ -966,6 +970,7 @@ const struct ethtool_ops gve_ethtool_ops = {
> .get_channels = gve_get_channels,
> .set_rxnfc = gve_set_rxnfc,
> .get_rxnfc = gve_get_rxnfc,
> + .get_rx_ring_count = gve_get_rx_ring_count,
> .get_rxfh_indir_size = gve_get_rxfh_indir_size,
> .get_rxfh_key_size = gve_get_rxfh_key_size,
> .get_rxfh = gve_get_rxfh,
>
> ---
> base-commit: 7b8e9264f55a9c320f398e337d215e68cca50131
> change-id: 20251222-gxring_google-d6c76c372f76
>
> Best regards,
> --
> Breno Leitao <leitao@debian.org>
>
next prev parent reply other threads:[~2025-12-23 4:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-22 17:16 [PATCH net-next] net: gve: convert to use .get_rx_ring_count Breno Leitao
2025-12-23 4:21 ` Subbaraya Sundeep [this message]
2025-12-23 5:22 ` Harshitha Ramamurthy
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=20251223042119.GA319551@kernel-ep2 \
--to=sbhatta@marvell.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hramamurthy@google.com \
--cc=joshwash@google.com \
--cc=kuba@kernel.org \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).