From: patchwork-bot+netdevbpf@kernel.org
To: Dimitri Daskalakis <dimitri.daskalakis1@gmail.com>
Cc: davem@davemloft.net, kuba@kernel.org, edumazet@google.com,
pabeni@redhat.com, andrew+netdev@lunn.ch, shuah@kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next] selftests: drv-net: Limit the max number of queues in procfs_downup_hammer
Date: Thu, 13 Nov 2025 02:10:05 +0000 [thread overview]
Message-ID: <176299980575.283263.10279512603610923655.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251111225319.3019542-1-dimitri.daskalakis1@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 11 Nov 2025 14:53:19 -0800 you wrote:
> For NICs with a large (1024+) number of queues, this test can cause
> excessive memory fragmentation. This results in OOM errors, and in the
> worst case driver/kernel crashes. We don't need to test with the max number
> of queues, just enough to create a high likelihood of races between
> reconfiguration and stats getting read.
>
> Signed-off-by: Dimitri Daskalakis <dimitri.daskalakis1@gmail.com>
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
>
> [...]
Here is the summary with links:
- [net-next] selftests: drv-net: Limit the max number of queues in procfs_downup_hammer
https://git.kernel.org/netdev/net-next/c/f766f8cdde01
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-11-13 2:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-11 22:53 [PATCH net-next] selftests: drv-net: Limit the max number of queues in procfs_downup_hammer Dimitri Daskalakis
2025-11-13 2:10 ` patchwork-bot+netdevbpf [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=176299980575.283263.10279512603610923655.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=dimitri.daskalakis1@gmail.com \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
/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.