public inbox for kdevops@lists.linux.dev
 help / color / mirror / Atom feed
From: cel@kernel.org
To: <kdevops@lists.linux.dev>
Cc: Chuck Lever <chuck.lever@oracle.com>
Subject: [PATCH 4/4] Update help text that mentions SIW
Date: Mon,  3 Jun 2024 12:06:58 -0400	[thread overview]
Message-ID: <20240603160658.4073204-5-cel@kernel.org> (raw)
In-Reply-To: <20240603160658.4073204-1-cel@kernel.org>

From: Chuck Lever <chuck.lever@oracle.com>

Generalize the help text, now that kdevops has two software RDMA
options.

Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
---
 workflows/fstests/nfs/Kconfig | 6 +++---
 workflows/gitr/nfs/Kconfig    | 3 +--
 2 files changed, 4 insertions(+), 5 deletions(-)

diff --git a/workflows/fstests/nfs/Kconfig b/workflows/fstests/nfs/Kconfig
index 9f47761712b2..926bc40b4559 100644
--- a/workflows/fstests/nfs/Kconfig
+++ b/workflows/fstests/nfs/Kconfig
@@ -50,9 +50,9 @@ config FSTESTS_NFS_SECTION_RDMA
 	bool "Enable testing section: nfs_rdma"
 	default n
 	help
-	  Enabling this will test with the "rdma" mount option. Unless the
-	  hosts have RDMA hardware already, you probably also want to enable
-	  CONFIG_KDEVOPS_SETUP_SIW as well.
+	  Enabling this will test with the "rdma" mount option. Unless
+	  the target nodes have RDMA hardware already, enable one of
+	  the software RDMA options as well.
 
 config FSTESTS_NFS_SECTION_TLS
 	bool "Enable testing section: nfs_tls"
diff --git a/workflows/gitr/nfs/Kconfig b/workflows/gitr/nfs/Kconfig
index a8c81b098957..1b1e53316ac7 100644
--- a/workflows/gitr/nfs/Kconfig
+++ b/workflows/gitr/nfs/Kconfig
@@ -38,8 +38,7 @@ config GITR_NFS_SECTION_RDMA
 	help
 	  Provision a target node to run the gitr workflow on a mount
 	  using NFS/RDMA. Unless your target nodes have RDMA hardware
-	  already, you are likely to need to enable the
-	  CONFIG_KDEVOPS_SETUP_SIW option as well.
+	  already, enable one of the software RDMA options as well.
 
 config GITR_NFS_SECTION_V42
 	bool "Enable testing section: nfs_v42"
-- 
2.45.1


  parent reply	other threads:[~2024-06-03 16:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-03 16:06 [PATCH 0/4] Add rxe as a second software RDMA option cel
2024-06-03 16:06 ` [PATCH 1/4] bringup.goals: Make siw settings more generic cel
2024-06-03 16:06 ` [PATCH 2/4] playbooks: Add a playbook to set up rxe on target nodes cel
2024-06-03 16:06 ` [PATCH 3/4] Kconfig: Add support for testing RDMA with software RoCE cel
2024-06-03 16:54   ` Zhu Yanjun
2024-06-07 13:10   ` Zhu Yanjun
2024-06-03 16:06 ` cel [this message]
2024-06-05 17:50 ` [PATCH 0/4] Add rxe as a second software RDMA option Chuck Lever III

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=20240603160658.4073204-5-cel@kernel.org \
    --to=cel@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=kdevops@lists.linux.dev \
    /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