From: Jakub Kicinski <kuba@kernel.org>
To: Gerhard Engleder <gerhard@engleder-embedded.com>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
netdev@vger.kernel.org, Oleksij Rempel <o.rempel@pengutronix.de>
Subject: Re: [PATCH net-next v9 6/8] net: selftests: Support selftest sets
Date: Mon, 3 Mar 2025 17:41:29 -0800 [thread overview]
Message-ID: <20250303174129.21aa5f88@kernel.org> (raw)
In-Reply-To: <20250227203138.60420-7-gerhard@engleder-embedded.com>
On Thu, 27 Feb 2025 21:31:36 +0100 Gerhard Engleder wrote:
> +/**
> + * enum net_selftest - selftest set ID
> + * @NET_SELFTEST_LOOPBACK_CARRIER: Loopback tests based on carrier speed
why are these "tests based on carrier speed"?
these tests use default parameters AFAICT, I'm not seeing the relevance
of carrier.. Maybe you can explain.
> + */
> +enum net_selftest {
> + NET_SELFTEST_LOOPBACK_CARRIER = 0,
> +};
> diff --git a/net/core/selftests.c b/net/core/selftests.c
> index e99ae983fca9..ec9bb149a378 100644
> --- a/net/core/selftests.c
> +++ b/net/core/selftests.c
> @@ -14,6 +14,10 @@
> #include <net/tcp.h>
> #include <net/udp.h>
>
> +struct net_test_ctx {
> + u8 next_id;
> +};
> +
> struct net_packet_attrs {
> const unsigned char *src;
> const unsigned char *dst;
> @@ -44,14 +48,13 @@ struct netsfhdr {
> u8 id;
> } __packed;
>
> -static u8 net_test_next_id;
The removal of the global state seems loosely connected to the rest,
the global state is okay because we hold RTNL across, AFAIU, which
will still be true for tests varying speed. Not using global state
is a worthwhile cleanup IMO, but I think you should split this patch
in 2.
next prev parent reply other threads:[~2025-03-04 1:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 20:31 [PATCH net-next v9 0/8] Support loopback mode speed selection Gerhard Engleder
2025-02-27 20:31 ` [PATCH net-next v9 1/8] net: phy: Allow loopback speed selection for PHY drivers Gerhard Engleder
2025-02-27 20:31 ` [PATCH net-next v9 2/8] net: phy: Support speed selection for PHY loopback Gerhard Engleder
2025-03-04 1:35 ` Jakub Kicinski
2025-03-04 13:20 ` Andrew Lunn
2025-03-04 16:15 ` Jakub Kicinski
2025-03-04 20:00 ` Gerhard Engleder
2025-03-06 5:58 ` Gerhard Engleder
2025-03-07 16:27 ` Andrew Lunn
2025-03-07 19:15 ` Gerhard Engleder
2025-03-11 5:39 ` Gerhard Engleder
2025-02-27 20:31 ` [PATCH net-next v9 3/8] net: phy: micrel: Add loopback support Gerhard Engleder
2025-02-27 20:31 ` [PATCH net-next v9 4/8] net: phy: marvell: Align set_loopback() implementation Gerhard Engleder
2025-02-27 20:31 ` [PATCH net-next v9 5/8] tsnep: Select speed for loopback Gerhard Engleder
2025-02-27 20:31 ` [PATCH net-next v9 6/8] net: selftests: Support selftest sets Gerhard Engleder
2025-03-04 1:41 ` Jakub Kicinski [this message]
2025-03-04 5:55 ` Gerhard Engleder
2025-02-27 20:31 ` [PATCH net-next v9 7/8] net: selftests: Add selftests sets with fixed speed Gerhard Engleder
2025-02-27 20:31 ` [PATCH net-next v9 8/8] tsnep: Add loopback selftests Gerhard Engleder
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=20250303174129.21aa5f88@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gerhard@engleder-embedded.com \
--cc=hkallweit1@gmail.com \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).