From: Yi Zhang <yi.zhang@redhat.com>
To: Sagi Grimberg <sagi@grimberg.me>,
linux-block@vger.kernel.org, Omar Sandoval <osandov@osandov.com>
Cc: linux-nvme@lists.infradead.org,
Logan Gunthorpe <logang@deltatee.com>,
Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>,
Keith Busch <kbusch@kernel.org>, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v7 7/7] nvme: support rdma transport type
Date: Sat, 5 Sep 2020 01:00:13 +0800 [thread overview]
Message-ID: <cd06eee5-d0e7-8dd5-1291-545f6cc0c31f@redhat.com> (raw)
In-Reply-To: <20200903235337.527880-8-sagi@grimberg.me>
On 9/4/20 7:53 AM, Sagi Grimberg wrote:
> Signed-off-by: Sagi Grimberg <sagi@grimberg.me>
> ---
> tests/nvme/rc | 20 ++++++++++++++++++++
> 1 file changed, 20 insertions(+)
>
> diff --git a/tests/nvme/rc b/tests/nvme/rc
> index 8df00e7d15d0..4c5b2e8edf0d 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 || _have_modules 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
> }
>
> _setup_nvmet() {
> @@ -124,6 +134,16 @@ _setup_nvmet() {
> modprobe nvmet-"${nvme_trtype}"
> fi
> modprobe nvme-"${nvme_trtype}"
> + if [[ "${nvme_trtype}" == "rdma" ]]; then
> + start_soft_rdma
> + for i in $(rdma_network_interfaces)
> + do
> + ipv4_addr=$(get_ipv4_addr "$i")
> + if [ -n "${ipv4_addr}" ]; then
> + def_traddr=${ipv4_addr}
Do we need add break here if ipv4_addr has value?
> + fi
> + done
> + fi
> }
>
> _nvme_disconnect_ctrl() {
next prev parent reply other threads:[~2020-09-04 17:00 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 23:53 [PATCH v7 0/7] blktests: Add support to run nvme tests with tcp/rdma transports Sagi Grimberg
2020-09-03 23:53 ` [PATCH v7 1/7] nvme: consolidate nvme requirements based on transport type Sagi Grimberg
2020-09-04 0:18 ` Chaitanya Kulkarni
2020-09-14 21:51 ` Omar Sandoval
2020-09-14 22:04 ` Logan Gunthorpe
2020-09-14 22:09 ` Omar Sandoval
2020-09-14 22:23 ` Logan Gunthorpe
2020-09-14 22:25 ` Omar Sandoval
2020-09-03 23:53 ` [PATCH v7 2/7] nvme: consolidate some nvme-cli utility functions Sagi Grimberg
2020-09-04 0:19 ` Chaitanya Kulkarni
2020-09-03 23:53 ` [PATCH v7 3/7] nvme: make tests transport type agnostic Sagi Grimberg
2020-09-04 0:20 ` Chaitanya Kulkarni
2020-09-03 23:53 ` [PATCH v7 4/7] tests/nvme: restrict tests to specific transports Sagi Grimberg
2020-09-04 0:21 ` Chaitanya Kulkarni
2020-09-14 21:53 ` Omar Sandoval
2020-09-03 23:53 ` [PATCH v7 5/7] nvme: support nvme-tcp when runinng tests Sagi Grimberg
2020-09-04 0:21 ` Chaitanya Kulkarni
2020-09-03 23:53 ` [PATCH v7 6/7] common: move module_unload to common Sagi Grimberg
2020-09-04 0:22 ` Chaitanya Kulkarni
2020-09-03 23:53 ` [PATCH v7 7/7] nvme: support rdma transport type Sagi Grimberg
2020-09-04 0:23 ` Chaitanya Kulkarni
2020-09-04 17:00 ` Yi Zhang [this message]
2020-09-04 15:52 ` [PATCH v7 0/7] blktests: Add support to run nvme tests with tcp/rdma transports Logan Gunthorpe
2020-09-11 22:06 ` Sagi Grimberg
2020-09-25 17:32 ` Omar Sandoval
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=cd06eee5-d0e7-8dd5-1291-545f6cc0c31f@redhat.com \
--to=yi.zhang@redhat.com \
--cc=Chaitanya.Kulkarni@wdc.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=logang@deltatee.com \
--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).