blob: ea6a851cdc50b27b3c735d11f9db3f25a67996f7 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
|
#
# For a description of the syntax of this configuration file,
# see misc/tools/kconfig-language.txt.
#
config NET_IOB
bool "Network I/O buffer support"
default n
---help---
This setting will build the networking I/O buffer (IOB) support
library.
if NET_IOB
config IOB_NBUFFERS
int "Number of pre-allocated network I/O buffers"
default 24
---help---
Each packet is represented by a series of small I/O buffers in a
chain. This setting determines the number of preallocated I/O
buffers available for packet data.
config IOB_BUFSIZE
int "Payload size of one network I/O buffer"
default 196
---help---
Each packet is represented by a series of small I/O buffers in a
chain. This setting determines the data payload each preallocated
I/O buffer.
config IOB_NCHAINS
int "Number of pre-allocated I/O buffer chain heads"
default 0
---help---
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. 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
|
