f5545d24b8
Don't allow CONFIG_INFINIBAND_IPOIB_DEBUG to be disabled unless CONFIG_EMBEDDED is selected. We want users (and especially distros) to have this turned on unless they really need to save space, because by the time we want debugging output, it's usually too late to rebuild a kernel. The debugging output can be controlled at runtime via the debug_level module parameter in sysfs. Signed-off-by: Roland Dreier <rolandd@cisco.com>
35 lines
1.3 KiB
Plaintext
35 lines
1.3 KiB
Plaintext
config INFINIBAND_IPOIB
|
|
tristate "IP-over-InfiniBand"
|
|
depends on INFINIBAND && NETDEVICES && INET
|
|
---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.
|
|
|
|
The IPoIB protocol is defined by the IETF ipoib working
|
|
group: <http://www.ietf.org/html.charters/ipoib-charter.html>.
|
|
|
|
config INFINIBAND_IPOIB_DEBUG
|
|
bool "IP-over-InfiniBand debugging" if EMBEDDED
|
|
depends on INFINIBAND_IPOIB
|
|
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 an "ipoib_debugfs," which can be
|
|
mounted to expose debugging information about IB multicast
|
|
groups used by the IPoIB driver.
|
|
|
|
config INFINIBAND_IPOIB_DEBUG_DATA
|
|
bool "IP-over-InfiniBand data path debugging"
|
|
depends on INFINIBAND_IPOIB_DEBUG
|
|
---help---
|
|
This option compiles debugging code into the 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.
|