From: Daniel Wagner <dwagner@suse.de>
To: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Cc: linux-block@vger.kernel.org, linux-nvme@lists.infradead.org,
Chaitanya Kulkarni <chaitanyak@nvidia.com>,
Hannes Reinecke <hare@suse.de>, Daniel Wagner <dwagner@suse.de>
Subject: [RFC blktests v1 05/10] nvme/rc: connect subsys only support long options
Date: Mon, 18 Mar 2024 10:38:50 +0100 [thread overview]
Message-ID: <20240318093856.22307-6-dwagner@suse.de> (raw)
In-Reply-To: <20240318093856.22307-1-dwagner@suse.de>
There is no user for the short command line options, thus
remove the short options to reduce the parsing overhead.
Signed-off-by: Daniel Wagner <dwagner@suse.de>
---
tests/nvme/rc | 26 +++++++++++++-------------
1 file changed, 13 insertions(+), 13 deletions(-)
diff --git a/tests/nvme/rc b/tests/nvme/rc
index c8f13819ca21..c23f6fe09b6a 100644
--- a/tests/nvme/rc
+++ b/tests/nvme/rc
@@ -440,55 +440,55 @@ _nvme_connect_subsys() {
while [[ $# -gt 0 ]]; do
case $1 in
- -a|--traddr)
+ --traddr)
traddr="$2"
shift 2
;;
- -w|--host-traddr)
+ --host-traddr)
host_traddr="$2"
shift 2
;;
- -s|--trsvcid)
+ --trsvcid)
trsvcid="$2"
shift 2
;;
- -n|--hostnqn)
+ --hostnqn)
hostnqn="$2"
shift 2
;;
- -I|--hostid)
+ --hostid)
hostid="$2"
shift 2
;;
- -S|--dhchap-secret)
+ --dhchap-secret)
hostkey="$2"
shift 2
;;
- -C|--dhchap-ctrl-secret)
+ --dhchap-ctrl-secret)
ctrlkey="$2"
shift 2
;;
- -i|--nr-io-queues)
+ --nr-io-queues)
nr_io_queues="$2"
shift 2
;;
- -W|--nr-write-queues)
+ --nr-write-queues)
nr_write_queues="$2"
shift 2
;;
- -P|--nr-poll-queues)
+ --nr-poll-queues)
nr_poll_queues="$2"
shift 2
;;
- -k|--keep-alive-tmo)
+ --keep-alive-tmo)
keep_alive_tmo="$2"
shift 2
;;
- -c|--reconnect-delay)
+ --reconnect-delay)
reconnect_delay="$2"
shift 2
;;
- -l|--ctrl-loss-tmo)
+ --ctrl-loss-tmo)
ctrl_loss_tmo="$2"
shift 2
;;
--
2.44.0
next prev parent reply other threads:[~2024-03-18 9:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 9:38 [RFC blktests v1 00/10] Add support to run against real target Daniel Wagner
2024-03-18 9:38 ` [RFC blktests v1 01/10] common/xfs: propagate errors from _xfs_run_fio_verify_io Daniel Wagner
2024-03-18 9:38 ` [RFC blktests v1 02/10] nvme/{012,013,035}: check return value of _xfs_run_fio_verify_io Daniel Wagner
2024-03-18 9:38 ` [RFC blktests v1 03/10] nvme/rc: use long command line option for nvme Daniel Wagner
2024-03-18 9:38 ` [RFC blktests v1 04/10] nvme/{014,015,018,019,020,023,024,026,045,046}: " Daniel Wagner
2024-03-18 9:38 ` Daniel Wagner [this message]
2024-03-18 9:38 ` [RFC blktests v1 06/10] nvme/rc: remove unused connect options Daniel Wagner
2024-03-18 9:38 ` [RFC blktests v1 06/10] nvme/rc: Remove " Daniel Wagner
2024-03-18 9:38 ` [RFC blktests v1 07/10] nvme/rc: add nqn/uuid args to target setup/cleanup helper Daniel Wagner
2024-03-18 9:38 ` [RFC blktests v1 08/10] nvme/031: do not open code target setup/cleanup Daniel Wagner
2024-03-18 9:38 ` [RFC blktests v1 09/10] nvme/rc: introduce remote target support Daniel Wagner
2024-03-18 9:38 ` [RFC blktests v1 10/10] nvme/030: only run against kernel soft target Daniel Wagner
2024-03-18 11:21 ` [RFC blktests v1 00/10] Add support to run against real target Daniel Wagner
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=20240318093856.22307-6-dwagner@suse.de \
--to=dwagner@suse.de \
--cc=chaitanyak@nvidia.com \
--cc=hare@suse.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=shinichiro.kawasaki@wdc.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