From: Jakub Kicinski <kuba@kernel.org>
To: Nimrod Oren <noren@nvidia.com>
Cc: Dragos Tatulea <dtatulea@nvidia.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [TEST] CX7 timeouts on reconfig w/ page pool failure injection
Date: Wed, 12 Aug 2026 09:59:47 -0700 [thread overview]
Message-ID: <20260812095947.3d0e6ca6@kernel.org> (raw)
In-Reply-To: <2d2aab62-a4fe-48eb-94e6-c8a0ec910ee9@nvidia.com>
On Wed, 12 Aug 2026 19:31:09 +0300 Nimrod Oren wrote:
> > 10min wasn't enough, bumping to 15min :(
>
> In these runs xdp-py took ~9.5 minutes. Both pp-alloc and rss-api tests
> passed:
>
> https://netdev.bots.linux.dev/logs/hwksft/CX7-dbg/results/774403/test-outputs/
> https://netdev.bots.linux.dev/logs/hwksft/CX7-dbg/results/774889/test-outputs/
> https://netdev.bots.linux.dev/logs/hwksft/CX7-dbg/results/775361/test-outputs/
Ack, I'll send a patch to bump the timeout shortly.
That said, the page pool warnings were probabilistic to begin with.
And they were hit in page_pool_unref_netmem(), I think _some_ bug
must still be there?
IOW mlx5e_page_release_fragmented() is draining more references than
the pp page use counter, that's not normal whether some command timeout
out or not.
next prev parent reply other threads:[~2026-08-12 16:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 16:45 [TEST] CX7 timeouts on reconfig w/ page pool failure injection Jakub Kicinski
2026-08-04 17:16 ` Dragos Tatulea
2026-08-04 19:44 ` Jakub Kicinski
2026-08-11 7:20 ` Nimrod Oren
2026-08-11 15:04 ` Jakub Kicinski
2026-08-11 16:57 ` Nimrod Oren
2026-08-11 17:38 ` Jakub Kicinski
2026-08-12 16:31 ` Nimrod Oren
2026-08-12 16:59 ` Jakub Kicinski [this message]
2026-08-12 19:48 ` Dragos Tatulea
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=20260812095947.3d0e6ca6@kernel.org \
--to=kuba@kernel.org \
--cc=dtatulea@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=noren@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.