From: Breno Leitao <leitao@debian.org>
To: hawk@kernel.org
Cc: netdev@vger.kernel.org, kernel-team@cloudflare.com,
"Jonas Köppeler" <j.koeppeler@tu-berlin.de>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Simon Horman" <horms@kernel.org>,
"Shuah Khan" <shuah@kernel.org>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next v3 5/5] selftests: net: add veth BQL stress test
Date: Fri, 1 May 2026 01:42:47 -0700 [thread overview]
Message-ID: <afRnXhsNMBRJ0LdB@gmail.com> (raw)
In-Reply-To: <20260429172036.1028526-6-hawk@kernel.org>
On Wed, Apr 29, 2026 at 07:20:32PM +0200, hawk@kernel.org wrote:
> +compile_tools() {
> + echo "--- Compiling UDP flood tool ---"
> +cat > "$TMPDIR"/udp_flood.c << 'CEOF'
The biggest structural issue: the test ships ~250 lines of C source as
heredocs and shells out to gcc at runtime to build them. This is not
how selftests normally work.
next prev parent reply other threads:[~2026-05-01 8:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-29 17:20 [PATCH net-next v3 0/5] veth: add Byte Queue Limits (BQL) support hawk
2026-04-29 17:20 ` [PATCH net-next v3 1/5] net: add dev->bql flag to allow BQL sysfs for IFF_NO_QUEUE devices hawk
2026-04-29 17:20 ` [PATCH net-next v3 2/5] veth: implement Byte Queue Limits (BQL) for latency reduction hawk
2026-04-29 17:20 ` [PATCH net-next v3 3/5] veth: add tx_timeout watchdog as BQL safety net hawk
2026-04-29 17:20 ` [PATCH net-next v3 4/5] net: sched: add timeout count to NETDEV WATCHDOG message hawk
2026-04-29 17:20 ` [PATCH net-next v3 5/5] selftests: net: add veth BQL stress test hawk
2026-05-01 2:00 ` Jakub Kicinski
2026-05-01 7:03 ` Jesper Dangaard Brouer
2026-05-01 8:42 ` Breno Leitao [this message]
2026-05-01 1:58 ` [PATCH net-next v3 0/5] veth: add Byte Queue Limits (BQL) support Jakub Kicinski
2026-05-01 7:28 ` Jesper Dangaard Brouer
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=afRnXhsNMBRJ0LdB@gmail.com \
--to=leitao@debian.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=horms@kernel.org \
--cc=j.koeppeler@tu-berlin.de \
--cc=kernel-team@cloudflare.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.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.