From: patchwork-bot+netdevbpf@kernel.org
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
edumazet@google.com, pabeni@redhat.com, horms@kernel.org,
andrew@lunn.ch, willemb@google.com
Subject: Re: [PATCH net-next v2] selftests: drv-net: so_txtime: only send test traffic to sch_etf
Date: Tue, 11 Aug 2026 01:20:10 +0000 [thread overview]
Message-ID: <178641121088.284305.16852894884064829291.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260808160129.890119-1-willemdebruijn.kernel@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 8 Aug 2026 12:00:44 -0400 you wrote:
> From: Willem de Bruijn <willemb@google.com>
>
> The ETF qdiscs drops traffic without a socket or txtime. Even with
> parameter skip_sock_check regular traffic is affected by ETF.
>
> This test ran fine when run manually in a pure software environment.
> But with drv-net across two hosts tests fail as early as when calling
> cfg.remote.deploy due to effectively losing connectivity.
>
> [...]
Here is the summary with links:
- [net-next,v2] selftests: drv-net: so_txtime: only send test traffic to sch_etf
https://git.kernel.org/netdev/net-next/c/ef3d6cca02c8
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2026-08-11 1:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-08 16:00 [PATCH net-next v2] selftests: drv-net: so_txtime: only send test traffic to sch_etf Willem de Bruijn
2026-08-11 1:20 ` patchwork-bot+netdevbpf [this message]
2026-08-11 1:31 ` Jakub Kicinski
2026-08-11 14:29 ` Willem de Bruijn
2026-08-11 15:27 ` Jakub Kicinski
2026-08-11 18:36 ` Willem de Bruijn
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=178641121088.284305.16852894884064829291.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemb@google.com \
--cc=willemdebruijn.kernel@gmail.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.