From: Sagi Grimberg <sagi@grimberg.me>
To: Keith Busch <kbusch@meta.com>,
linux-block@vger.kernel.org, axboe@kernel.dk,
linux-nvme@lists.infradead.org, hch@lst.de
Cc: Keith Busch <kbusch@kernel.org>
Subject: Re: [PATCH 0/3] nvme fabrics polling fixes
Date: Wed, 22 Mar 2023 09:31:12 +0200 [thread overview]
Message-ID: <2027b975-1c9e-eb92-e374-9719bad49869@grimberg.me> (raw)
In-Reply-To: <20230322002350.4038048-1-kbusch@meta.com>
> I couldn't test the existing tcp
It is very simple to do, for tcp you can just operate on the loopback
iface 127.0.0.1
See example:
$ ./target.sh 1 1
$ nvme connect-all -t tcp -a 127.0.0.1 -P 1
For rdma you can work on any interface you want, you just need
iproute with rdma utility (which is available with recent iproute
packages).
Setup Software RoCE:
$ rdma link add rxe0 type rxe netdev <iface>
Setup Software iWarp:
$ rdma link add siw0 type siw netdev <iface>
Then the same as before...
$ ./target.sh 1 1
$ nvme connect-all -t tcp -a <iface-addr> -P 1
That is essentially what blktest do.
target.sh
--
#!/bin/bash
# args: <num_subsys> <nr_ns-per-subsystem> <nvme|file>
# examples:
# - ./target.sh 1 1 # uses null_blk
# - ./target.sh 1 1 nvme
# - ./target.sh 1 1 file
CFGFS=/sys/kernel/config/nvmet
NQN=testnqn
mount -t configfs configfs /sys/kernel/config > /dev/null 2>&1
rm -f $CFGFS/ports/*/subsystems/*
rm -f $CFGFS/subsystems/*/allowed_hosts/* > /dev/null 2>&1
rmdir $CFGFS/subsystems/*/namespaces/* > /dev/null 2>&1
rmdir $CFGFS/subsystems/* > /dev/null 2>&1
rmdir $CFGFS/ports/* > /dev/null 2>&1
rmdir $CFGFS/hosts/* > /dev/null 2>&1
modprobe -r nvmet_rdma nvmet-tcp > /dev/null 2>&1
modprobe -r ib_umad rdma_ucm ib_uverbs rdma_cm > /dev/null 2>&1
modprobe -r null_blk nvme-tcp nvme-rdma
modprobe -r nvme-loop
rm -f /tmp/nsf*
if [[ $1 == "0" ]]; then
exit
fi
modprobe null_blk nr_devices=$2 #queue_mode=0 irqmode=0
modprobe -a nvmet_tcp nvmet_rdma
mkdir $CFGFS/ports/1
echo 0.0.0.0 > $CFGFS/ports/1/addr_traddr
echo 8009 > $CFGFS/ports/1/addr_trsvcid
echo "tcp" > $CFGFS/ports/1/addr_trtype
echo "ipv4" > $CFGFS/ports/1/addr_adrfam
mkdir $CFGFS/ports/2
echo 0.0.0.0 > $CFGFS/ports/2/addr_traddr
echo 4420 > $CFGFS/ports/2/addr_trsvcid
echo "rdma" > $CFGFS/ports/2/addr_trtype
echo "ipv4" > $CFGFS/ports/2/addr_adrfam
mkdir $CFGFS/ports/3
echo "loop" > $CFGFS/ports/3/addr_trtype
for j in `seq $1`
do
mkdir $CFGFS/subsystems/$NQN$j
echo 1 > $CFGFS/subsystems/$NQN$j/attr_allow_any_host
k=0
for i in `seq $2`
do
mkdir $CFGFS/subsystems/$NQN$j/namespaces/$i
if [[ "$3" == "nvme" ]]; then
echo -n "/dev/nvme0n1" >
$CFGFS/subsystems/$NQN$j/namespaces/$i/device_path
elif [[ "$3" == "file" ]]; then
ns="/tmp/nsf$k"
touch $ns
truncate --size=2G $ns
echo -n "$ns" >
$CFGFS/subsystems/$NQN$j/namespaces/$i/device_path
else
echo -n "/dev/nullb$k" >
$CFGFS/subsystems/$NQN$j/namespaces/$i/device_path
fi
echo 1 > $CFGFS/subsystems/$NQN$j/namespaces/$i/enable
let "k+=1"
done
ln -s $CFGFS/subsystems/$NQN$j $CFGFS/ports/1/subsystems/
ln -s $CFGFS/subsystems/$NQN$j $CFGFS/ports/2/subsystems/
ln -s $CFGFS/subsystems/$NQN$j $CFGFS/ports/3/subsystems/
done
--
next prev parent reply other threads:[~2023-03-22 7:31 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 0:23 [PATCH 0/3] nvme fabrics polling fixes Keith Busch
2023-03-22 0:23 ` [PATCH 1/3] nvme-fabrics: add queue setup helpers Keith Busch
2023-03-22 1:46 ` Chaitanya Kulkarni
2023-03-22 4:38 ` kernel test robot
2023-03-22 5:21 ` Chaitanya Kulkarni
2023-03-22 7:35 ` Sagi Grimberg
2023-03-22 8:27 ` Christoph Hellwig
2023-03-22 9:07 ` Sagi Grimberg
2023-03-22 9:25 ` kernel test robot
2023-03-22 0:23 ` [PATCH 2/3] nvme: add polling options for loop target Keith Busch
2023-03-22 1:47 ` Chaitanya Kulkarni
2023-03-22 7:44 ` Sagi Grimberg
2023-03-22 8:23 ` Christoph Hellwig
2023-03-22 8:46 ` Daniel Wagner
2023-03-22 13:52 ` Christoph Hellwig
2023-03-22 14:06 ` Daniel Wagner
2023-03-22 14:20 ` Christoph Hellwig
2023-03-22 14:30 ` Keith Busch
2023-03-22 0:23 ` [PATCH 3/3] blk-mq: directly poll requests Keith Busch
2023-03-22 7:36 ` Sagi Grimberg
2023-03-22 8:23 ` Christoph Hellwig
2023-03-22 9:08 ` Sagi Grimberg
2023-03-22 8:37 ` Daniel Wagner
2023-03-22 18:16 ` Chaitanya Kulkarni
2023-03-31 7:57 ` Shinichiro Kawasaki
2023-03-22 7:31 ` Sagi Grimberg [this message]
2023-03-22 8:48 ` [PATCH 0/3] nvme fabrics polling fixes Daniel Wagner
2023-03-22 13:24 ` 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=2027b975-1c9e-eb92-e374-9719bad49869@grimberg.me \
--to=sagi@grimberg.me \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=kbusch@meta.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
/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