Hi Joseph, > -----Original Message----- > From: linux-rdma-owner@xxxxxxxxxxxxxxx [mailto:linux-rdma- > owner@xxxxxxxxxxxxxxx] On Behalf Of Gruher, Joseph R > Sent: Friday, February 02, 2018 1:19 PM > To: linux-rdma@xxxxxxxxxxxxxxx > Subject: How to tell RoCE v1 vs v2? > > > Hi folks- > > We're doing some NVMeoF testing. We have Xeon servers with Mellanox CX4 > NICs connected through an Arista 7060CX switch. We're using the kernel > support for RDMA and NVMeoF in Ubuntu 16.10 with a 4.12.5 kernel. I'm trying > to figure out if we're running RoCE v1 or RoCE v2. I can't seem to Google up a > way to check when running the kernel solution, just answers for Mellanox OFED. > Is there a way to tell? And if we're running v1, is there a way to force v2? Steps: mkdir /sys/kernel/config/rdma_cm/mlx5_0 cat /sys/kernel/config/rdma_cm/mlx5_0/ports/1/default_roce_mode #Above command tells whether default is RoCEv1 or v2. echo "RoCE v2" > /sys/kernel/config/rdma_cm/mlx5_0/ports/1/default_roce_mode Above command will force to pick RoCEv2 GIDs by default when using RDMACM based applications (if HCA supports it). RoCEv2 was made default in below patch. commit 3c7f67d1880db4bda8eed12ca603c92b5434390e Author: Doug Ledford <dledford@xxxxxxxxxx> Date: Fri Jul 28 13:47:24 2017 -0400 IB/cma: Fix default RoCE type setting The initial patch for changing the stack to use RoCEv2 GIDs by default set the CMA_PREFERRED_ROCE_GID_TYPE to an incorrect value. Instead of an absolute value, we needed to set the right bit in a bitmask. Correct the default setting so we use RoCEv2 by default. Fixes: 63a5f483af0e (IB/cma: Set default gid type to RoCEv2) Signed-off-by: Doug Ledford <dledford@xxxxxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
