config [31mCONFIG_INFINIBAND_IPOIB[0m tristate "IP-over-InfiniBand" depends on [31mCONFIG_NETDEVICES[0m && [31mCONFIG_INET[0m && ([31mCONFIG_IPV6[0m || [31mCONFIG_IPV6[0m=n) ---help--- Support for the IP-over-InfiniBand protocol (IPoIB). This transports IP packets over InfiniBand so you can use your IB device as a fancy NIC. See Documentation/infiniband/ipoib.txt for more information config [31mCONFIG_INFINIBAND_IPOIB_CM[0m bool "IP-over-InfiniBand Connected Mode support" depends on [31mCONFIG_INFINIBAND_IPOIB[0m default n ---help--- This option enables support for IPoIB connected mode. After enabling this option, you need to switch to connected mode through /sys/class/net/ibXXX/mode to actually create connections, and then increase the interface MTU with e.g. ifconfig ib0 mtu 65520. WARNING: Enabling connected mode will trigger some packet drops for multicast and UD mode traffic from this interface, unless you limit mtu for these destinations to 2044. config [31mCONFIG_INFINIBAND_IPOIB_DEBUG[0m bool "IP-over-InfiniBand debugging" if [31mCONFIG_EXPERT[0m depends on [31mCONFIG_INFINIBAND_IPOIB[0m default y ---help--- This option causes debugging code to be compiled into the IPoIB driver. The output can be turned on via the debug_level and mcast_debug_level module parameters (which can also be set after the driver is loaded through sysfs). This option also creates a directory tree under ipoib/ in debugfs, which contains files that expose debugging information about IB multicast groups used by the IPoIB driver. config [31mCONFIG_INFINIBAND_IPOIB_DEBUG_DATA[0m bool "IP-over-InfiniBand data path debugging" depends on [31mCONFIG_INFINIBAND_IPOIB_DEBUG[0m ---help--- This option compiles debugging code into the data path of the IPoIB driver. The output can be turned on via the data_debug_level module parameter; however, even with output turned off, this debugging code will have some performance impact. |