From: Allison Henderson <achender@kernel.org>
To: netdev@vger.kernel.org, pabeni@redhat.com, edumazet@google.com,
kuba@kernel.org, horms@kernel.org, linux-rdma@vger.kernel.org,
achender@kernel.org, linux-kselftest@vger.kernel.org,
shuah@kernel.org
Subject: [PATCH net-next v1 0/3] selftests: rds: ROCE support follow ups
Date: Fri, 22 May 2026 14:54:27 -0700 [thread overview]
Message-ID: <20260522215430.3748226-1-achender@kernel.org> (raw)
Hi all,
This is a follow up series to the "Add ROCE support to rds selftests"
series. The first patch renames run.sh to rds_run.sh, and also adds
two wrappers to the TEST_PROGS target to run the same test over the
rdma and tcp transports. The wrappers rds_rdma_run.sh and
rds_tcp_run.sh also provide self-describing names that appear on the
netdev CI dashboard.
The second patch addresses a sashiko complaint that I thought was worth
circling back for. In the patch "pin RDS sockets to their intended
transport," sockets are pinned the specific transport they are meant to
test. By default, socket transports are implicitly selected based on
the network topology, but it is possible that they can fail back to
other transports if the underlying connection could not be established.
So the patch pins them to the intended transport to avoid false
positives.
Lastly the third patch "support RDS built as loadable module," lifts
the CONFIG_MODULES=n requirement, and updates the check_*conf_enabled()
to allow modules set to "=m" and further load the backing modules for
any component set as such.
Questions, comments and feedback appreciated!
Thanks everyone!
Allison
Allison Henderson (3):
selftests: rds: add per-transport run wrappers
selftests: rds: pin RDS sockets to their intended transport
selftests: rds: support RDS built as loadable modules
tools/testing/selftests/net/rds/Makefile | 6 +-
tools/testing/selftests/net/rds/README.txt | 13 ++--
tools/testing/selftests/net/rds/config | 1 -
.../testing/selftests/net/rds/rds_rdma_run.sh | 11 ++++
.../selftests/net/rds/{run.sh => rds_run.sh} | 63 ++++++++++++-------
.../testing/selftests/net/rds/rds_tcp_run.sh | 11 ++++
tools/testing/selftests/net/rds/test.py | 18 ++++++
7 files changed, 95 insertions(+), 28 deletions(-)
create mode 100755 tools/testing/selftests/net/rds/rds_rdma_run.sh
rename tools/testing/selftests/net/rds/{run.sh => rds_run.sh} (80%)
create mode 100755 tools/testing/selftests/net/rds/rds_tcp_run.sh
--
2.25.1
next reply other threads:[~2026-05-22 21:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-22 21:54 Allison Henderson [this message]
2026-05-22 21:54 ` [PATCH net-next v1 1/3] selftests: rds: add per-transport run wrappers Allison Henderson
2026-05-22 21:54 ` [PATCH net-next v1 2/3] selftests: rds: pin RDS sockets to their intended transport Allison Henderson
2026-05-22 21:54 ` [PATCH net-next v1 3/3] selftests: rds: support RDS built as loadable modules Allison Henderson
2026-05-23 0:46 ` [PATCH net-next v1 0/3] selftests: rds: ROCE support follow ups Jakub Kicinski
2026-05-23 1:19 ` Allison Henderson
2026-05-23 2:14 ` Jakub Kicinski
2026-05-23 2:26 ` Allison Henderson
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=20260522215430.3748226-1-achender@kernel.org \
--to=achender@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-rdma@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox