Lines Matching refs:network
10 This document describes how various network configuration options can be
16 The network buffer configuration options control how much data we
20 Maximum amount of network packets we can receive at the same time.
23 Maximum amount of network packet sends pending at the same time.
26 How many network buffers are allocated for receiving data.
34 can be the amount of data we have received from the network.
35 When data is received from the network, it is placed into net_buf data portion.
36 Depending on device resources and desired network usage, user can tweak
41 When using the fixed size data buffers, the memory consumption of network buffers
42 can be tweaked by selecting the size of the data part according to what kind of network
47 network buffer size is set to 128 bytes.
52 data we need for the network data. The extra cost here is the amount of time
62 How many network buffers are allocated for sending data. This is similar setting
70 This option tells how many network connection endpoints are supported.
74 The network shell command **net conn** can be used at runtime to see the
75 network connection information.
78 Number of network contexts to allocate. Each network context describes a network
79 5-tuple that is used when listening or sending network traffic. Each BSD socket in the
80 system uses one network context.
138 Maximum number of IPv4 network interfaces in the system.
139 This tells how many network interfaces there will be in the system
141 For example if you have two network interfaces, but only one of them
143 If both network interface could use IPv4, then the setting should be
147 Maximum number of IPv6 network interfaces in the system.
199 according to amount of network buffers configured in the system.
210 according to amount of network buffers configured in the system.
231 or sending network data. Each traffic class queue is implemented as a thread
232 with different priority. This means that higher priority network packet can
233 be placed to a higher priority network queue in order to send or receive it
243 class queue. Reason is that typically the network device driver is running
245 to deliver the network packet directly to the upper layers, but to place
246 the packet to the traffic class queue. If the network device driver is not
254 There several network specific threads in a network enabled system.
257 to allow normal network operations.
259 The network management API is using a dedicated thread by default. The thread
260 is responsible to deliver network management events to the event listeners that
264 that the net_mgmt thread is calling for each network management event.
272 The network thread stack utilization can be monitored from kernel shell by