[rds-devel] [PATCH net-next v1 0/2] selftests: rds: refactor and expand rds selftests test

[Allison Henderson]

On Mon, 2026-03-02 at 17:33 -0800, Jakub Kicinski wrote:
> On Sun,  1 Mar 2026 22:55:16 -0700 Allison Henderson wrote:
> > This series aims to improve the current rds selftests.  The first patch
> > refactors the existing test.py such that the networking set up can be
> > reused as general purpose infrastructure for other tests.  The existing
> > send and receive code is hoisted into a separate rds_basic.py.  The next
> > patch adds a new rds_stress.py that exercises RDS via the external
> > rds-stress tool from the rds-tools package if it is available on the host.
> > We add two new flags to test.py, -b and -s to select rds_basic or
> > rds_stress respectively.  The intent is to make the RDS selftests more
> > modular and extensible.  Let me know what you all think.
> > 
> > Questions, comments, suggestions appreciated!
> 
> IDK Allison. I tried to integrate the remaining tests with Netdev CI
> this weekend. The two groups of networking tests which can't be run
> like all the other selftests are vsock and RDS. I get vsock being
> different. vsock is used to communicate between VMs and host, setting
> up the vms with the locally built kernel makes it different.
> 
> But I'm not exactly sure what makes RDS different. Would you mind
> explaining the challenges with fitting RDS into the ksft framework?

Hi Jakub,

I didnt know it was causing you grief, but I am happy to work with you to adapt it.  RDS is a little unique in that the
network topology defines the underlying transport it uses.  If you were to run it with just a pair of veth interfaces on
a single host or vm, then you will only be using the loop back transport in rds.ko.  In order to get it to load and test
rds_tcp.ko, we need the endpoints to be in separate network namespaces so that the destination IP isn't seen as local. 
So the test case does this by forking server/client processes across name spaces.  There really isnt a rush on this
series, so if you think we should do some refactoring/cleanup for ksft first that is fine.  Let me know your thoughts.

Thanks,
Allison