From: Jakub Kicinski <kuba@kernel.org>
To: Vimlesh Kumar <vimleshk@marvell.com>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<sedara@marvell.com>, <srasheed@marvell.com>, <hgani@marvell.com>
Subject: Re: [PATCH RESEND net v3 0/3] disable interrupts and ensure dbell updation
Date: Mon, 2 Feb 2026 18:03:52 -0800 [thread overview]
Message-ID: <20260202180352.513e6eb1@kernel.org> (raw)
In-Reply-To: <20260130141549.827020-1-vimleshk@marvell.com>
On Fri, 30 Jan 2026 14:15:44 +0000 Vimlesh Kumar wrote:
> Disable per ring interrupts when netdev goes down and ensure dbell BADDR
> updation for both PFs and VFs by adding wait and check for updated value.
>
> Resending based on discussion with reviewer.
Looking more closely at this I think the issue Simon flagged is real.
The caller cleans up only the rings for which the init succeeded:
int octep_setup_oqs(struct octep_device *oct)
{
int i, retval = 0;
oct->num_oqs = 0;
for (i = 0; i < CFG_GET_PORTS_ACTIVE_IO_RINGS(oct->conf); i++) {
retval = octep_setup_oq(oct, i);
if (retval) {
dev_err(&oct->pdev->dev,
"Failed to setup OQ(RxQ)-%d.\n", i);
goto oq_setup_err;
}
dev_dbg(&oct->pdev->dev, "Successfully setup OQ(RxQ)-%d.\n", i);
}
return 0;
oq_setup_err:
while (i) {
i--;
octep_free_oq(oct->oq[i]);
}
return -1;
prev parent reply other threads:[~2026-02-03 2:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 14:15 [PATCH RESEND net v3 0/3] disable interrupts and ensure dbell updation Vimlesh Kumar
2026-01-30 14:15 ` [PATCH RESEND net v3 1/3] octeon_ep: disable per ring interrupts Vimlesh Kumar
2026-02-03 2:04 ` Jakub Kicinski
2026-01-30 14:15 ` [PATCH RESEND net v3 2/3] octeon_ep: ensure dbell BADDR updation Vimlesh Kumar
2026-01-30 14:15 ` [PATCH RESEND net v3 3/3] octeon_ep_vf: " Vimlesh Kumar
2026-02-03 2:03 ` 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=20260202180352.513e6eb1@kernel.org \
--to=kuba@kernel.org \
--cc=hgani@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sedara@marvell.com \
--cc=srasheed@marvell.com \
--cc=vimleshk@marvell.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