From: Yi Zhang <yi.zhang@redhat.com>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>,
linux-nvme@lists.infradead.org, linux-block@vger.kernel.org,
Johannes Thumshirn <jthumshirn@suse.de>,
Keith Busch <kbusch@kernel.org>,
Omar Sandoval <osandov@osandov.com>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH rfc 6/6] nvme: support rdma transport type
Date: Wed, 5 Aug 2020 16:57:56 +0800 [thread overview]
Message-ID: <6edfbfd4-106e-f200-2783-d59615f0a84c@redhat.com> (raw)
In-Reply-To: <20200803064835.67927-7-sagi@grimberg.me>
On 8/3/20 2:48 PM, Sagi Grimberg wrote:
> Signed-off-by: Sagi Grimberg <sagi@grimberg.me>
> ---
> tests/nvme/rc | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> diff --git a/tests/nvme/rc b/tests/nvme/rc
> index 69ab7d2f3964..31d02fefa70e 100644
> --- a/tests/nvme/rc
> +++ b/tests/nvme/rc
> @@ -5,6 +5,7 @@
> # Test specific to NVMe devices
>
> . common/rc
> +. common/multipath-over-rdma
>
> def_traddr="127.0.0.1"
> def_adrfam="ipv4"
> @@ -25,6 +26,12 @@ _nvme_requires() {
> _have_modules nvmet nvme-core nvme-tcp nvmet-tcp
> _have_configfs
> ;;
> + rdma)
> + _have_modules nvmet nvme-core nvme-rdma nvmet-rdma
> + _have_configfs
> + _have_program rdma
> + _have_modules rdma_rxe siw
> + ;;
> *)
> SKIP_REASON="unsupported nvme_trtype=${nvme_trtype}"
> return 1
> @@ -115,6 +122,9 @@ _cleanup_nvmet() {
> modprobe -r nvmet-${nvme_trtype} 2>/dev/null
> fi
> modprobe -r nvmet 2>/dev/null
> + if [[ "${nvme_trtype}" == "rdma" ]]; then
> + stop_soft_rdma
> + fi
> }
>
# nvme_trtype=rdma ./check nvme/030
nvme/030 (ensure the discovery generation counter is updated appropriately)
nvme/030 (ensure the discovery generation counter is updated
appropriately) [passed]
runtime 0.616s ... 0.520s 460: unload_module: command not found
The unload_module[1] was defined in [2], how about move the definition
to [3],
[1]
_cleanup_nvmet->stop_soft_rdma->unload_module
[2]
./tests/nvmeof-mp/rc
[3]
common/multipath-over-rdma
> _setup_nvmet() {
> @@ -124,6 +134,11 @@ _setup_nvmet() {
> modprobe nvmet-${nvme_trtype}
> fi
> modprobe nvme-${nvme_trtype}
> + if [[ "${nvme_trtype}" == "rdma" ]]; then
> + start_soft_rdma
> + rdma_intfs=$(rdma_network_interfaces)
> + def_traddr=$(get_ipv4_addr ${rdma_intfs[0]})
> + fi
> }
>
> _nvme_disconnect_ctrl() {
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2020-08-05 8:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-03 6:48 [PATCH rfc 0/6] blktests: Add support to run nvme tests with tcp/rdma transports Sagi Grimberg
2020-08-03 6:48 ` [PATCH rfc 1/6] nvme: consolidate nvme requirements based on transport type Sagi Grimberg
2020-08-03 7:13 ` Johannes Thumshirn
2020-08-03 6:48 ` [PATCH rfc 2/6] nvme: consolidate some nvme-cli utility functions Sagi Grimberg
2020-08-03 7:12 ` Johannes Thumshirn
2020-08-03 6:48 ` [PATCH rfc 3/6] nvme: make tests transport type agnostic Sagi Grimberg
2020-08-03 6:48 ` [PATCH rfc 4/6] tests/nvme: restrict tests to specific transports Sagi Grimberg
2020-08-03 6:48 ` [PATCH rfc 5/6] nvme: support nvme-tcp when runinng tests Sagi Grimberg
2020-08-03 6:48 ` [PATCH rfc 6/6] nvme: support rdma transport type Sagi Grimberg
2020-08-05 8:57 ` Yi Zhang [this message]
2020-08-05 17:59 ` Sagi Grimberg
2020-08-03 20:16 ` [PATCH rfc 0/6] blktests: Add support to run nvme tests with tcp/rdma transports Chaitanya Kulkarni
2020-08-04 15:37 ` Sagi Grimberg
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=6edfbfd4-106e-f200-2783-d59615f0a84c@redhat.com \
--to=yi.zhang@redhat.com \
--cc=Chaitanya.Kulkarni@wdc.com \
--cc=hch@lst.de \
--cc=jthumshirn@suse.de \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=osandov@osandov.com \
--cc=sagi@grimberg.me \
/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;
as well as URLs for NNTP newsgroup(s).