no CONFIG_BQL

[PATCH] net: make CONFIG_BQL actually end user configurable

Without the defining string or help text, LKC won't ever bother
to ask the end user for a setting for CONFIG_BQL -- you could
delete it from your .config and run make oldconfig and not a
thing would change -- it would still be silently re-enabled.

While most people will have no reason to turn this off, the
ability to do so can be useful for testing BQL support additions
on previously BQL-unaware drivers and similar.

The kconfig help text is largely taken from the original RFC
patchset 0/N header sent to netdev <at> vger.kernel.org in fall 2011.

Signed-off-by: Paul Gortmaker <paul.gortmaker <at> windriver.com>
---

[Apologies if this was explicitly blocked for a reason; I couldn't
 find a reason after searching netdev or threads at bufferbloat.net ]

diff --git a/net/Kconfig b/net/Kconfig
index e07272d..fd1d815 100644
--- a/net/Kconfig
+++ b/net/Kconfig
 <at>  <at>  -241,10 +241,15  <at>  <at>  config NETPRIO_CGROUP
 	  a per-interface basis

 config BQL
-	boolean
+	boolean	"Byte Queue Limits"
 	depends on SYSFS
 	select DQL
 	default y
+	---help---
+	  Byte queue limits are a mechanism to limit the size of the transmit
+	  hardware queue on a NIC by a number of bytes. The goal of these byte
+	  queue limits is to reduce latency caused by excessive queuing in
+	  hardware without sacrificing throughput.

http://permalink.gmane.org/gmane.linux.network/223087