From: Jakub Kicinski <kuba@kernel.org>
To: Vikas Gupta <vikas.gupta@broadcom.com>
Cc: davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
andrew+netdev@lunn.ch, horms@kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, bhargava.marreddy@broadcom.com,
rahul-rg.gupta@broadcom.com, vsrama-krishna.nemani@broadcom.com,
rajashekar.hudumula@broadcom.com, dharmender.garg@broadcom.com,
ajit.khaparde@broadcom.com
Subject: Re: [PATCH net v2] bnge: add missing ndo_set_features
Date: Thu, 27 Aug 2026 09:42:57 -0700 [thread overview]
Message-ID: <20260827094257.610ece67@kernel.org> (raw)
In-Reply-To: <20260827161230.1724658-1-vikas.gupta@broadcom.com>
On Thu, 27 Aug 2026 21:42:30 +0530 Vikas Gupta wrote:
> + bnge_close_core(bn);
> + bn->priv_flags = flags;
> + bnge_set_ring_params(bd);
> +
> + rc = bnge_open_core(bn);
> + if (rc) {
> + netdev_err(dev, "bnge_open_core err: %d\n", rc);
> + bn->priv_flags = old_flags;
> + bnge_set_ring_params(bd);
> + netif_close(dev);
We have been requiring NIC reconfiguration to be resilient against
OOM conditions for years now. bnxt is even older so it got
grandfathered in, but bnge has to do it right. So we will reject
any patch that tries to close / reopen and hope for the best.
If you want a net fix - you should reflect current operation
of the driver - meaning make GRO-HW either forced on or forced off.
(Forced on by leaving it in the netdev->features but not in
->hw_features). Or reject changes while the device is UP
--
pw-bot: cr
prev parent reply other threads:[~2026-08-27 16:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-27 16:12 Vikas Gupta
2026-08-27 16:42 ` Jakub Kicinski [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=20260827094257.610ece67@kernel.org \
--to=kuba@kernel.org \
--cc=ajit.khaparde@broadcom.com \
--cc=andrew+netdev@lunn.ch \
--cc=bhargava.marreddy@broadcom.com \
--cc=davem@davemloft.net \
--cc=dharmender.garg@broadcom.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rahul-rg.gupta@broadcom.com \
--cc=rajashekar.hudumula@broadcom.com \
--cc=vikas.gupta@broadcom.com \
--cc=vsrama-krishna.nemani@broadcom.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
all inboxes | Powered by JetHome®