Differences

This shows you the differences between two versions of the page.

--- nndocs:srp [2025/02/14 12:56] – created naptastic
+++ nndocs:srp [2025/11/08 06:12] (current) – target/ACL confusion reduction naptastic
@@ Line 1: / Line 1: @@
 ====targetcli-fb====
-The documentation for SRP is woefully inadequte.
+  * it needs to be turned on in the kernel. drivers -> Infiniband -> SRP
+  * turn on both target and initiator please
+  * in targetcli, /srpt is the relevant path
+  * targets are formatted like ib.fe80000000000000f4521403002c18b1
+  * idk how you get those numbers except to examine an ipoib link, such as:
-  /srpt> ib.fe800000000000005849560e53b70b01/acls create
+: ib0: <...> mtu 2044 ...
-  Missing required parameter wwn
+      link/infiniband 80:00:02:18:fe:80:00:00:00:00:00:00:f4:52:14:03:00:2c:18:b1
-  /srpt> ib.fe800000000000005849560e53b70b01/acls create wwn=ib.800000000000005849560e53b70b01
+      brd             00:ff:ff:ff:ff:12:40:1b:ff:ff:00:00:00:00:00:00:ff:ff:ff:ff
-  WWN not valid as: ib
-  /srpt> ib.fe800000000000005849560e53b70b01/acls create wwn=800000000000005849560e53b70b01
-  WWN not valid as: ib
-From man targetcli(8):
+Now strip the first 4 bytes off (they change anyway) and remove the :'s
-  CONFIGURING SRP
+  fe800000000000005849560e59150301
-         SRP (SCSI RDMA Protocol) requires that RDMA-capable hardware is present. It uses "ib" WWNs.
-NONE OF THIS TELLS ME HOW TO FORMAT THE STRING. Let's go spelunking in the kernel, I guess...
+Initiator ACLs start with all 0's. Targets start with fe80.
+  /srpt> ib.fe800000000000005849560e53b70b01/acls create ib.00000000000000005849560e59150301
+  Created Node ACL for ib.00000000000000005849560e59150301
+  Created mapped LUN 0.
+A Linux SRP target is always visible from all InfiniBand partitions.
+====Dependencies====
+  apt install srptools
+Do **NOT** set srp_daemon loose without using the -o flag! It will flood dmesg on both the initiator and the target!
+Find targets to connect to:
+    # srp_daemon -o -v -c -p 1
+  * -o means "run once" otherwise dmesg on all your hosts will get polluted with SRP login noise.
+  * -v means "say what you're doing"
+  * -c means "emit target information in a format we can use later"
+  * -p 1 means "only scan on HCA port 1" so obviously change this if you are initiating from port 2...
+====Configuration====
+It is **critical** that you edit /etc/srp_daemon.conf as soon as you have a list of targets and disallow connections to anything except the targets you want. The default file is well commented.
+To connect to a target listed by srp_daemon, write it to the appropriate add_target file in /sys/class/infiniband_srp. Here's how shark gets its swap ramdisk from southpark:
+  echo 'id_ext=5849560e53b70b01,ioc_guid=5849560e53b70b01,dgid=fe800000000000005849560e53b70b01,pkey=ffff,service_id=5849560e53b70b01' > /sys/class/infiniband_srp/srp-ibp14s0f0-1/add_target
+Lazy benchmarking seems good:
+  [root]@[shark][~]# dd if=/dev/sdb of=/dev/null bs=4M
++0 records in
++0 records out
+  17179869184 bytes (17 GB, 16 GiB) copied, 5.38771 s, 3.2 GB/s
+  [root]@[shark][~]# dd if=/dev/zero of=/dev/sdb bs=4M
+  dd: error writing '/dev/sdb': No space left on device
++0 records in
++0 records out
+  17179869184 bytes (17 GB, 16 GiB) copied, 13.7431 s, 1.3 GB/s
+====Logout====
+"Delete the port" sounds pretty destructive, but this actually is the graceful way to close the connection.
+  # echo 1 > /sys/class/srp_remote_ports/[tab tab tab]/delete