From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, andrew+netdev@lunn.ch, horms@kernel.org,
willemb@google.com, anubhavsinggh@google.com,
mohsin.bashr@gmail.com, shuah@kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next] selftests: drv-net: gro: increase the rcvbuf size
Date: Sat, 10 Jan 2026 01:40:15 +0000 [thread overview]
Message-ID: <176800921502.446502.17034098573250179681.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260107232557.2147760-1-kuba@kernel.org>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 7 Jan 2026 15:25:57 -0800 you wrote:
> The gro.py test (testing software GRO) is slightly flaky when
> running against fbnic. We see one flake per roughly 20 runs in NIPA,
> mostly in ipip.large, and always including some EAGAIN:
>
> # Shouldn't coalesce if exceed IP max pkt size: Test succeeded
> # Expected {65475 899 }, Total 2 packets
> # Received {65475 899 }, Total 2 packets.
> # Expected {64576 900 900 }, Total 3 packets
> # Received {64576 /home/virtme/testing/wt-24/tools/testing/selftests/drivers/net/gro: could not receive: Resource temporarily unavailable
>
> [...]
Here is the summary with links:
- [net-next] selftests: drv-net: gro: increase the rcvbuf size
https://git.kernel.org/netdev/net-next/c/a0ac0ff38276
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:[~2026-01-10 1:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-07 23:25 [PATCH net-next] selftests: drv-net: gro: increase the rcvbuf size Jakub Kicinski
2026-01-07 23:51 ` Willem de Bruijn
2026-01-10 1:40 ` 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=176800921502.446502.17034098573250179681.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=anubhavsinggh@google.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mohsin.bashr@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--cc=willemb@google.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.