Differences

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

--- nndocs:infiniband [2024/03/14 20:16] – [Upper-Layer Protocols (ULPs)] expand VMA section naptastic
+++ nndocs:infiniband [2026/08/09 06:35] (current) – Move GUIDs to their pages naptastic
@@ Line 1: / Line 1: @@
 =====InfiniBand=====
-Configuration is a real pain. On my Debian hosts, it's all in /etc/rc.local, which is gross. I haven't figured out how to do it on Ubuntu, since Netplan apparently has support for vxlan and ipoib now, I think. **We'll get there**.
+Configuration is a real pain. On my Debian hosts, it's all in /etc/rc.local, which is gross. I haven't figured out how to do it on Ubuntu, since Netplan apparently has support for vxlan and IP over IB (IPoIB) now, I think. **We'll get there**.
+  * [[nndocs::infiniband::ConnectX-3]]
+  * [[nndocs::infiniband::Connect-IB]]
+  * [[nndocs::infiniband::ConnectX-4]]
+  * [[SX6005]]
+  * [[SX6036]]
 ===The Problem===
-All the InfiniBand hardware I have is Mellanox FDR-generation, so, ConnectX-3, Connect-IB, and SX60xx IB-only switches. The officially-supported distribution overlay only supports Debian through 11, RHEL through 8, and Ubuntu through 20.04, **OR** ConnectX-4 or newer cards only. The newer drivers won't even load for CX-3 or C-IB adapters.
+All the InfiniBand hardware I have is Mellanox FDR-generation.
+For hardware support, Mellanox provides MLNX_OFED, an overlay for several distributions. Unfortunately, MLNX_OFED only supports Debian through 11, RHEL through 8, and Ubuntu through 20.04, **OR** ConnectX-4 or newer cards only. The drivers built into Linux still recognize and work with ConnectX-3 and Connect-IB, but the kernel drivers in MLNX_OFED don't. They just show up as unclaimed PCI devices.
-^ MLNX_OFED version ^ Minimum hardware ^ Debian ^ Ubuntu ^ OpenSM version ^
+^ Version ^ Minimum hardware ^ Debian ^ Ubuntu ^ OpenSM version ^
 | Inbox |  | All | All | 3.3.23-2 |
-| 4.9-x | ConnectX-2 | ≤ 11 | ≤ 20.04 | 5.7.2 |
+| MLNX_OFED 4.9-x | ConnectX-2 | ≤ 11 | ≤ 20.04 | 5.7.2 |
-| 5.8-x | ConnectX-4 | ≥ 9 | ≥ 18.04 | 5.17.0 |
+| MLNX_OFED 5.8-x | ConnectX-4 | ≥ 9 | ≥ 18.04 | 5.17.0 |
 ===How I'm Getting Around It===
 "Inbox" (distribution-provided) drivers and utilities are basically good enough, and probably will probably support my hardware until I'm ready to throw it away.
 ====The Inbox Part====
@@ Line 27: / Line 35: @@
 ====The MLNX part====
-There may be other parts of MLNX_OFED worth stealing; I haven't tried. It is possible to install OpenSM 5.7 from OFED 4.9. From this path run this command:
+Old OpenSM has this annoying problem where, if the HCA goes away while OpenSM is running, it will start to spew into its logfile, and it will run the system out of disk space. I don't know when it got fixed, but as of August 2024 it doesn't do that anymore.
-    MLNX_OFED_LINUX-4.9-7.1.0.0-ubuntu20.04-x86_64/DEBS/MLNX_LIBS# dpkg -i opensm*deb libopensm*deb libibumad*deb
+    MLNX_OFED_LINUX-24.07-0.6.1.0-debian12.5-x86_64/DEBS# dpkg -i opensm*deb libopensm*deb libibumad*deb
 There's also ibdump, with which you must be very careful: it really does capture everything!
-    # dpkg -i ibdump_6.0.0-1.49710_amd64.deb
+    # dpkg -i ibdump_6.0.0-1.2407061_amd64.deb
-=====SR-IOV=====
+=====The Subnet Manager: OpenSM=====
-====OpenSM Configuration====
+====Virtualization====
 For virtualization to work, you have to be using Mellanox's OpenSM fork. When I installed it and ran `opensm -c` to create its default configuration, it had this block in it:
@@ Line 47: / Line 55: @@
     virt_enabled 2
-In partitions.conf, well, just make the defualt partition look like this:
+====Partitions: OpenSM configuration====
+Atop an InfiniBand fabric, one or more partitions must be defined for hosts to join before they can communicate. IB has a concept of "full" and "partial" membership. Full members can communicate with any other host in the partition. Partial members can communicate with full members, but not with each other. Whether a host is a full or partial member is controlled by the high bit of the partition number. There's also a "both" option. I can't come up with a use case for "both".
-    Default=0x7fff, ipoib, rate=12, mtu=5, scope=2, defmember=full:
+Linux has very limited support for partial membership. It's best to give all hosts in a partition full membership. Partial membership is probably useful if you have Windows guests and want to keep them isolated at a layer 2 level; I have no need to play in that playground.
-        mgid=ff12:401b::ffff:ffff   # IPv4 Broadcast address
-        mgid=ff12:401b::1           # IPv4 All Hosts group
-        mgid=ff12:401b::2           # IPv4 All Routers group
-        mgid=ff12:401b::16          # IPv4 IGMP group
-        mgid=ff12:401b::fb          # IPv4 mDNS group
-        mgid=ff12:401b::fc          # IPv4 Multicast Link Local Name Resolution group
-        mgid=ff12:401b::101         # IPv4 NTP group
-        mgid=ff12:401b::202         # IPv4 Sun RPC
-        mgid=ff12:601b::1           # IPv6 All Hosts group
-        mgid=ff12:601b::2           # IPv6 All Routers group
-        mgid=ff12:601b::16          # IPv6 MLDv2-capable Routers group
-        mgid=ff12:601b::fb          # IPv6 mDNS group
-        mgid=ff12:601b::101         # IPv6 NTP group
-        mgid=ff12:601b::202         # IPv6 Sun RPC group
-        mgid=ff12:601b::1:3         # IPv6 Multicast Link Local Name Resolution group
-        ALL=full, ALL_SWITCHES=full;
-It's important to use "full" and not "both" or "limited" for every group membership. Otherwise VFs inside VMs will have a pkey of 0x8000 which is invalid, and they'll show NO-CARRIER.
+The default partition configuration sucks. Make it look like this:
-====Hardware Settings====
+  Default=0x7fff, ipoib, rate=12, mtu=5, scope=2, defmember=full:
-The BIOS needs to have SR-IOV, ARI, and ACS support enabled.
+      mgid=ff12:401b::ffff:ffff   # IPv4 Broadcast address
+      mgid=ff12:401b::1           # IPv4 All Hosts group
+      mgid=ff12:401b::2           # IPv4 All Routers group
+      mgid=ff12:401b::16          # IPv4 IGMP group
+      mgid=ff12:401b::fb          # IPv4 mDNS group
+      mgid=ff12:401b::fc          # IPv4 Multicast Link Local Name Resolution group
+      mgid=ff12:401b::101         # IPv4 NTP group
+      mgid=ff12:401b::202         # IPv4 Sun RPC
+      mgid=ff12:601b::1           # IPv6 All Hosts group
+      mgid=ff12:601b::2           # IPv6 All Routers group
+      mgid=ff12:601b::16          # IPv6 MLDv2-capable Routers group
+      mgid=ff12:601b::fb          # IPv6 mDNS group
+      mgid=ff12:601b::101         # IPv6 NTP group
+      mgid=ff12:601b::202         # IPv6 Sun RPC group
+      mgid=ff12:601b::1:3         # IPv6 Multicast Link Local Name Resolution group
+      ALL=full, ALL_SWITCHES=full;
-On Connect-IB cards, these firmware options need to be set:
+The default config file lists rates through QDR. For FDR and newer rates, see include/iba/ib_types.h in the OpenSM source repository. They're listed as parameters to ib_path_rec_rate() in the comments below the sub declarition. 12 is correct for FDR x4 links. (Wider links are only possible between managed switches. Support for narrower links got removed at some point.)
-    NUM_OF_VFS                                  7
-    NUM_OF_PF                                   1
-    FPP_EN                                      True(1)
-    SRIOV_EN                                    True(1)
-FPP_EN (Flow Priority something) controls whether the card appears as two PCI devices, or as a single device with two ports. Under mlx4, every VF on a dual-port HCA has both ports, and NUM_OF_VFs is how many dual-port devices to create. Under mlx5, each port gets its own pool of VFs and NUM_OF_VFs is per-port.
+Here's a block for my ATA over Ethernet experiments. Subject to change. IP addresses are necessary for setting up VXLAN tunnels. Checking if IPv6 tunnels perform differently from IPv4 tunnels is on the to-do list. I suspect they perform better. Needs testing.
-I haven't tried large numbers of VFs. The hardware upper limit is 63 for Connect-IB and 127 for ConnectX-3. Firmware might have a lower limit than that. I don't expect to need that many guests with IOV networking...
+  storage=0xb128, ipoib, rate=12, mtu=5, scope=2, defmember=full:
+      mgid=ff12:401b::ffff:ffff   # IPv4 Broadcast address
+      mgid=ff12:401b::1           # IPv4 All Hosts group
+      ALL=full, ALL_SWITCHES=full;
-After a reboot, there should be a new file, /sys/bus/pci/devices/0000:b:d:f/sriov_numvfs. Try turning it on. If it works, there will be new PCI devices as well as VFs listed under `ip link`:
+====Partitions: Host configuration====
+There's no functional netlink interface for creating child interfaces. You must use the sysfs interface.
+  # echo 0xb128 > /sys/class/net/ib0/create_child
-    # echo 7 > /sys/class/infiniband/ibp6s0f0/device/sriov_numvfs # no output on success; check dmesg for interesting but probably useless messages.
+Resist the temptation to rename the interface to something descriptive. **It's already self-descriptive**. Creative naming is for VXLAN tunnels and bridges, e.g.:
-    # lspci | grep nfi
-:00.0 Infiniband controller: Mellanox Technologies MT27600 [Connect-IB]
-:00.1 Infiniband controller: Mellanox Technologies MT27600 [Connect-IB]
-:00.2 Infiniband controller: Mellanox Technologies MT27600 Family [Connect-IB Virtual Function]
-:00.3 Infiniband controller: Mellanox Technologies MT27600 Family [Connect-IB Virtual Function]
-:00.4 Infiniband controller: Mellanox Technologies MT27600 Family [Connect-IB Virtual Function]
-:00.5 Infiniband controller: Mellanox Technologies MT27600 Family [Connect-IB Virtual Function]
-:00.6 Infiniband controller: Mellanox Technologies MT27600 Family [Connect-IB Virtual Function]
-:00.7 Infiniband controller: Mellanox Technologies MT27600 Family [Connect-IB Virtual Function]
-:01.0 Infiniband controller: Mellanox Technologies MT27600 Family [Connect-IB Virtual Function]
-Warning: The output from ip link is very wide.
+  # ip link add vx128 type vxlan id 128 local 172.20.128.13 group 225.172.20.128
+  # ip link set master aoe1 dev vx128
-    # ip link
+The sysfs interface for deleting child interfaces doesn't work (for me at least). You must use the netlink interface.
-: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
+  # ip link del ib0.b128
-        link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
-: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
-        link/ether 3c:ec:ef:6d:10:62 brd ff:ff:ff:ff:ff:ff
-: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
-        link/ether 3c:ec:ef:6d:10:63 brd ff:ff:ff:ff:ff:ff
-: ib0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 4092 qdisc fq_codel state UP mode DEFAULT group default qlen 256
-        link/infiniband 80:00:00:29:fe:80:00:00:00:00:00:00:58:49:56:0e:53:b7:0b:01 brd 00:ff:ff:ff:ff:12:40:1b:ff:ff:00:00:00:00:00:00:ff:ff:ff:ff
-        vf 0     link/infiniband 80:00:00:29:fe:80:00:00:00:00:00:00:58:49:56:0e:53:b7:0b:01 brd 00:ff:ff:ff:ff:12:40:1b:ff:ff:00:00:00:00:00:00:ff:ff:ff:ff, spoof checking off, NODE_GUID 00:00:00:00:00:00:00:00, PORT_GUID 00:00:00:00:00:00:00:00, link-state disable, trust off, query_rss off
-        vf 1     link/infiniband 80:00:00:29:fe:80:00:00:00:00:00:00:58:49:56:0e:53:b7:0b:01 brd 00:ff:ff:ff:ff:12:40:1b:ff:ff:00:00:00:00:00:00:ff:ff:ff:ff, spoof checking off, NODE_GUID 00:00:00:00:00:00:00:00, PORT_GUID 00:00:00:00:00:00:00:00, link-state disable, trust off, query_rss off
-        vf 2     link/infiniband 80:00:00:29:fe:80:00:00:00:00:00:00:58:49:56:0e:53:b7:0b:01 brd 00:ff:ff:ff:ff:12:40:1b:ff:ff:00:00:00:00:00:00:ff:ff:ff:ff, spoof checking off, NODE_GUID 00:00:00:00:00:00:00:00, PORT_GUID 00:00:00:00:00:00:00:00, link-state disable, trust off, query_rss off
-        vf 3     link/infiniband 80:00:00:29:fe:80:00:00:00:00:00:00:58:49:56:0e:53:b7:0b:01 brd 00:ff:ff:ff:ff:12:40:1b:ff:ff:00:00:00:00:00:00:ff:ff:ff:ff, spoof checking off, NODE_GUID 00:00:00:00:00:00:00:00, PORT_GUID 00:00:00:00:00:00:00:00, link-state disable, trust off, query_rss off
-        vf 4     link/infiniband 80:00:00:29:fe:80:00:00:00:00:00:00:58:49:56:0e:53:b7:0b:01 brd 00:ff:ff:ff:ff:12:40:1b:ff:ff:00:00:00:00:00:00:ff:ff:ff:ff, spoof checking off, NODE_GUID 00:00:00:00:00:00:00:00, PORT_GUID 00:00:00:00:00:00:00:00, link-state disable, trust off, query_rss off
-        vf 5     link/infiniband 80:00:00:29:fe:80:00:00:00:00:00:00:58:49:56:0e:53:b7:0b:01 brd 00:ff:ff:ff:ff:12:40:1b:ff:ff:00:00:00:00:00:00:ff:ff:ff:ff, spoof checking off, NODE_GUID 00:00:00:00:00:00:00:00, PORT_GUID 00:00:00:00:00:00:00:00, link-state disable, trust off, query_rss off
-        vf 6     link/infiniband 80:00:00:29:fe:80:00:00:00:00:00:00:58:49:56:0e:53:b7:0b:01 brd 00:ff:ff:ff:ff:12:40:1b:ff:ff:00:00:00:00:00:00:ff:ff:ff:ff, spoof checking off, NODE_GUID 00:00:00:00:00:00:00:00, PORT_GUID 00:00:00:00:00:00:00:00, link-state disable, trust off, query_rss off
-: ib1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 4092 qdisc fq_codel state DOWN mode DEFAULT group default qlen 256
-        link/infiniband 80:00:00:28:fe:80:00:00:00:00:00:00:58:49:56:0e:53:b7:0b:09 brd 00:ff:ff:ff:ff:12:40:1b:ff:ff:00:00:00:00:00:00:ff:ff:ff:ff
-: ib2: <BROADCAST,MULTICAST> mtu 4092 qdisc noop state DOWN mode DEFAULT group default qlen 256
-        link/infiniband 80:00:00:27:fe:80:00:00:00:00:00:00:00:00:00:00:00:00:00:00 brd 00:ff:ff:ff:ff:12:40:1b:ff:ff:00:00:00:00:00:00:ff:ff:ff:ff
-: ib3: <BROADCAST,MULTICAST> mtu 4092 qdisc noop state DOWN mode DEFAULT group default qlen 256
-        link/infiniband 80:00:00:27:fe:80:00:00:00:00:00:00:00:00:00:00:00:00:00:00 brd 00:ff:ff:ff:ff:12:40:1b:ff:ff:00:00:00:00:00:00:ff:ff:ff:ff
-: ib4: <BROADCAST,MULTICAST> mtu 4092 qdisc noop state DOWN mode DEFAULT group default qlen 256
-        link/infiniband 80:00:00:27:fe:80:00:00:00:00:00:00:00:00:00:00:00:00:00:00 brd 00:ff:ff:ff:ff:12:40:1b:ff:ff:00:00:00:00:00:00:ff:ff:ff:ff
-: ib5: <BROADCAST,MULTICAST> mtu 4092 qdisc noop state DOWN mode DEFAULT group default qlen 256
-        link/infiniband 80:00:00:27:fe:80:00:00:00:00:00:00:00:00:00:00:00:00:00:00 brd 00:ff:ff:ff:ff:12:40:1b:ff:ff:00:00:00:00:00:00:ff:ff:ff:ff
-: ib6: <BROADCAST,MULTICAST> mtu 4092 qdisc noop state DOWN mode DEFAULT group default qlen 256
-        link/infiniband 80:00:00:27:fe:80:00:00:00:00:00:00:00:00:00:00:00:00:00:00 brd 00:ff:ff:ff:ff:12:40:1b:ff:ff:00:00:00:00:00:00:ff:ff:ff:ff
-: ib7: <BROADCAST,MULTICAST> mtu 4092 qdisc noop state DOWN mode DEFAULT group default qlen 256
-        link/infiniband 80:00:00:27:fe:80:00:00:00:00:00:00:00:00:00:00:00:00:00:00 brd 00:ff:ff:ff:ff:12:40:1b:ff:ff:00:00:00:00:00:00:ff:ff:ff:ff
-: ib8: <BROADCAST,MULTICAST> mtu 4092 qdisc noop state DOWN mode DEFAULT group default qlen 256
-        link/infiniband 80:00:00:27:fe:80:00:00:00:00:00:00:00:00:00:00:00:00:00:00 brd 00:ff:ff:ff:ff:12:40:1b:ff:ff:00:00:00:00:00:00:ff:ff:ff:ff
-====VF Configuration====
+If you unset the high bit on the partition number (0x3128 instead of 0xb128) Linux will set the high bit before joining the partition. If OpenSM's configuration has that partition's membership set for "partial" or "both", the Linux host will not be able to connect to everything on that subnet, or possibly //anything// on that subnet, regardless of which value you use.
-To set the GUID for VFs:
-    ip link set dev ib0 vf 0 node_guid 58:49:56:0e:53:b7:0b:02
+====Connected vs. Datagram====
-    ip link set dev ib0 vf 0 port_guid 58:49:56:0e:53:b7:0b:02
+IPoIB can run in one of three modes:
-    ip link set dev ib0 vf 0 state enable
+  - Datagram, in which the IP MTU matches the subnet MTU. Performance is pretty trash.
+  - Connected, in which the MTU is limited only by kernel and network structures. Practically, this means 64k, or 65520 bytes after protocol overhead is accounted for. Performance for some workloads is greatly improved.
+  - Enhanced, which is not compatible with Connected mode, but has more offloads and is (from what I hear) generally better.
+    * Enhanced IPoIB is only available on ConnectX-4 and newer cards.
-Make port_guid == node_guid == unique. (I use the base port guid + VF + 1.)
+IPoIB is still a dog, performance-wise. It's a very fast, very expensive winmodem. It should be thought of as a way of getting IP addresses, which you then use to set up RDMA-aware protocols.
+As far as I can tell, IPoIB interfaces are always created in datagram mode. The documentation says that Connect-IB cards default to connected mode; that has not been my experience. There's also no way to set connected mode as the default when the module is loaded, or otherwise ensure that interfaces get created in connected mode. Before changing modes, the interface must be down. The netlink interface for setting the connection mode has not worked for me; I might just be doing it wrong:
+  # ip link set mode connected ib0.b129
+  Error: argument "connected" is wrong: Invalid link mode
+  # ^connected^datagram
+  ip link set mode datagram ib0.b129
+  Error: argument "datagram" is wrong: Invalid link mode
+The sysfs interface works:
+  # echo connected > /sys/class/net/ib0.b129/mode
+Since I don't have any newer hardware, I don't have any information about Enhanced IPoIB.
+=====SR-IOV=====
+====Hardware Settings====
+The BIOS needs to have SR-IOV, ARI, and ACS support enabled.
+On Connect-IB cards, these firmware options need to be set:
+    NUM_OF_VFS                                  7
+    NUM_OF_PF                                   1
+    FPP_EN                                      True(1)
+    SRIOV_EN                                    True(1)
+FPP_EN (Function Per Port ENable) controls whether the card appears as two PCI devices, or as a single device with two ports. Under mlx5, each port gets its own pool of VFs and NUM_OF_VFs is per-port.
+I haven't tried large numbers of VFs. The hardware upper limit is 63 for Connect-IB and 127 for ConnectX-3. Any number of system components could impose lower limits. I don't expect to need so many guests with IOV networking anyway...
-Lazy copy-pasta for shark:
-    ip link set dev ib0 vf 0 node_guid 58:49:56:0e:59:11:02:02
-    ip link set dev ib0 vf 0 port_guid 58:49:56:0e:59:11:02:02
-    ip link set dev ib0 vf 0 state enable
 =====Upper-Layer Protocols (ULPs)=====
-RDMA opens all kinds of possibilities for RDMA-aware protocols to be amazing and fast.
+RDMA opens all kinds of possibilities for RDMA-aware protocols to be amazing and fast. They probably all deserve their own pages.
+===IP over InfiniBand (IPoIB)===
+It's already been used on this page extensively. IPoIB encapsulates IP traffic in InfiniBand datagrams so that protocols built for Ethernet (primarily TCP and UDP) can run on IB networks. Performance is generally poor. There are some hacks to make it faster, but the real reason to use IPoIB is to give your IB hosts IP addresses for setting up other ULPs.
 ===VMA===
@@ Line 152: / Line 150: @@
   * Apache
   * PHP
-  * MySQL
+  * MySQL (though I think MySQL has its own RDMA backend?)
   * SSH (and consequently rsync and scp, right?)
+    * (It would also be cool to find out if newer cards with crypto functions could do hardware-accelerated SSH with RDMA.)
 None of these services is so performance-critical that I'll spend time configuring it for VMA, except maybe as a learning exercise. **Later**.
 ====Storage====
   * NFS/RDMA (probably needs a page)
@@ Line 163: / Line 163: @@
   * See [[iSCSI]] for information about enabling and using iSER.
   * See [[NVMe-oF]] for using NVMe over InfiniBand.
-  * I'm curious about the performance of SRP. I have gotten it to work before but it's not working now. Also not a huge priority.
+  * [[SRP]] is fast but the documentation is a joke.
 ====Networking====
 ===VXLAN===
-VXLAN is not the only way to get an Ethernet device on Infiniband, but as far as I can tell it's the only decent one. Neither ConnectX-3 nor Connect-IB has VXLAN offload support so it's like a Winmodem but the number is a million times bigger.
+VXLAN is not the only way to get an Ethernet device on Infiniband, but as far as I can tell it's the only decent one.
+ConnectX-3 Pro, ConnectX-4, and newer Mellanox cards have VXLAN offloading support, but only for Ethernet ports. So VXLAN overlays are always going to be done by the CPU. They're still decently fast.
   * VXLAN id can be anything from 0-16777215 inclusive. I make it match the network number.
@@ Line 176: / Line 179: @@
     export vxlan=64
-    export vxlan_name=ibnet0 # this doesn't get used by anything or stored anywhere
     export local=172.20.64.9
     export group=225.172.20.64
-    ip link add name vxlan64 type vxlan id 64 local 172.20.64.10 group 225.172.20.64 dev ib0 dstport 0
+    export dev=ib0
+    ip link add name vxlan$id type vxlan id $id local $local group $group dev $dev dstport 0
-If/when I get hardware capable of VXLAN offload, the dstport might have to change.
 Once the VNI exists, it can be added to a bridge:
@@ Line 188: / Line 189: @@
 //Et viola//, Ethernet on top of InfiniBand.
+Note: The Infiniband MTU is 4k; IPoIB takes 4 bytes and VXLAN takes 50, leaving a max MTU of 4042.
 ====Multimedia====
-Yeah, someday I want to throw video frames around. There's an RFC or ISO standard for that, IIRC. There's also lgproxy.
+Yeah, someday I want to throw video frames around. There's an RFC or ISO standard for that, IIRC. There's also lgproxy, which is RDMA-aware.
 I also want to throw audio frames around with "no latency added". Someday, someday, someday.
+====GUIDs====
+GUIDs and MAC addresses for Mellanox cards are listed on their respective pages. These two are ancient Qlogic adapters. I've never gotten them to work on my network; I pretty much just bought them to destroy and learn.
+  * 001175000079b560 - uninstalled qib
+  * 001175000079b856 - uninstalled qib