public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Allison Henderson <achender@kernel.org>
Cc: netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
	pabeni@redhat.com, edumazet@google.com, rds-devel@oss.oracle.com,
	horms@kernel.org, linux-rdma@vger.kernel.org,
	allison.henderson@oracle.com
Subject: Re: [PATCH net-next v1 0/2] selftests: rds: refactor and expand rds selftests test
Date: Mon, 2 Mar 2026 17:33:02 -0800	[thread overview]
Message-ID: <20260302173302.4d1634be@kernel.org> (raw)
In-Reply-To: <20260302055518.301620-1-achender@kernel.org>

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?

  parent reply	other threads:[~2026-03-03  1:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-02  5:55 [PATCH net-next v1 0/2] selftests: rds: refactor and expand rds selftests test Allison Henderson
2026-03-02  5:55 ` [PATCH net-next v1 1/2] selftests: rds: Refactor test.py Allison Henderson
2026-03-02  5:55 ` [PATCH net-next v1 2/2] selftests: rds: Add rds_stress.py Allison Henderson
2026-03-03  1:33 ` Jakub Kicinski [this message]
2026-03-04  2:50   ` [PATCH net-next v1 0/2] selftests: rds: refactor and expand rds selftests test Allison Henderson
2026-03-04 18:32     ` Jakub Kicinski
2026-03-06  7:43       ` Allison Henderson
2026-03-06 20:07         ` Jakub Kicinski

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=20260302173302.4d1634be@kernel.org \
    --to=kuba@kernel.org \
    --cc=achender@kernel.org \
    --cc=allison.henderson@oracle.com \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rds-devel@oss.oracle.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