summaryrefslogtreecommitdiff
path: root/nuttx/net/iob/Kconfig
diff options
context:
space:
mode:
Diffstat (limited to 'nuttx/net/iob/Kconfig')
-rw-r--r--nuttx/net/iob/Kconfig23
1 files changed, 20 insertions, 3 deletions
diff --git a/nuttx/net/iob/Kconfig b/nuttx/net/iob/Kconfig
index f7793afa8..ea6a851cd 100644
--- a/nuttx/net/iob/Kconfig
+++ b/nuttx/net/iob/Kconfig
@@ -30,10 +30,27 @@ config IOB_BUFSIZE
config IOB_NCHAINS
int "Number of pre-allocated I/O buffer chain heads"
- default 8
+ default 0
---help---
- These tiny nodes are used as "containers" to suppor queueing of
+ These tiny nodes are used as "containers" to support queueing of
I/O buffer chains. This will limit the number of I/O transactions
- that can be "in-flight" at any give time.
+ that can be "in-flight" at any give time. The default value of
+ zero disables this features.
+
+ These generic I/O buffer chain containers are not currently used
+ by any logic in NuttX. That is because their other other specialized
+ I/O buffer chain containers that also carry a payload of usage
+ specific information.
+
+config NET_IOB_DEBUG
+ bool "Force I/O buffer debug"
+ default n
+ depends on DEBUG
+ ---help---
+ This option will force debug output from I/O buffer logic,
+ even without network debug output. This is not normally something
+ that would want to do but is convenient if you are debugging the
+ I/O buffer logic and do not want to get overloaded with other
+ network-related debug output.
endif # NET_IOB