Linux-2.6.12-rc2v2.6.12-rc2

Initial git repository build. I'm not bothering with the full history,
even though we have it. We can create a separate "historical" git
archive of that later if we want to, and in the meantime it's about
3.2GB when imported into git - space that would just make the early
git days unnecessarily complicated, when we don't have a lot of good
infrastructure for it.

Let it rip!

1 files changed, 33 insertions, 0 deletions

diff --git a/drivers/infiniband/ulp/ipoib/Kconfig b/drivers/infiniband/ulp/ipoib/Kconfig
new file mode 100644
index 000000000000..8d2e04cac68e
--- /dev/null
+++ b/drivers/infiniband/ulp/ipoib/Kconfig
@@ -0,0 +1,33 @@
+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"
+        depends on INFINIBAND_IPOIB
+        ---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.