Searched full:traffic (Results 1 – 25 of 157) sorted by relevance
1234567
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | traffic-class.rst | 3 Traffic Classification
9 `Traffic classification <https://en.wikipedia.org/wiki/Traffic_classification>`_
10 is an automated process that categorizes computer network traffic according to
15 By default, all network traffic is treated equal in Zephyr. If desired, the
18 the number of receive queues. Each traffic class queue corresponds to a
20 The VLAN priority is mapped to a certain traffic class according to rules
22 and chapter 34.5 table 34-1. Each traffic class is in turn mapped to a certain
23 kernel work queue. The maximum number of traffic classes for both Rx and Tx
|
| D | system_mgmt.rst | 19 traffic-class.rst
|
| D | zperf.rst | 3 zperf: Network Traffic Generator
13 zperf is a shell utility which allows to generate network traffic in Zephyr. The
|
| D | capture.rst | 14 traffic in one of the Zephyr network interfaces and send that traffic to
22 network traffic for a given network interface. If you would like to capture
|
| /Zephyr-latest/subsys/net/ip/ |
| D | net_tc.c | 22 * or "RX" denoting receive thread. The "q[y]" denotes the traffic class queue
23 * where y indicates the traffic class id. The value of y can be from 0 to 7.
128 /* Convert traffic class to thread priority */
131 /* Initial implementation just maps the traffic class to certain queue. in tx_tc2thread()
139 * Higher traffic class value means higher priority queue. This means in tx_tc2thread()
144 * traffic classes, then this priority array will contain following in tx_tc2thread()
159 * This means that the lowest traffic class 1, will have the lowest in tx_tc2thread()
168 "Too many traffic classes"); in tx_tc2thread()
177 /* Convert traffic class to thread priority */
185 "Too many traffic classes"); in rx_tc2thread()
[all …]
|
| D | Kconfig | 351 int "How many Tx traffic classes to have for each network device"
361 Define how many Tx traffic classes (queues) the system should have
363 be mapped to this traffic class so that higher prioritized packets
367 The default value is 1 which means that all the network traffic is
368 handled equally. In this implementation, the higher traffic class
370 If you select 0 here, then it means that all the network traffic
376 int "How many Rx traffic classes to have for each network device"
383 Define how many Rx traffic classes (queues) the system should have
385 be mapped to this traffic class so that higher prioritized packets
389 The default value is 1 which means that all the network traffic is
[all …]
|
| D | net_tc_mapping.h | 2 * @brief Various priority to traffic class mappings
21 * Priority Acronym Traffic types
38 /* This is the recommended priority to traffic class mapping for
78 /* This is the recommended priority to traffic class mapping for a system that
114 /* This is the recommended priority to traffic class mapping for a system that
|
| D | Kconfig.debug | 62 module-str = Log level for network traffic class code
63 module-help = Enables network traffic class code to output debug messages.
|
| /Zephyr-latest/drivers/wifi/nrf_wifi/inc/ |
| D | coex_struct.h | 26 /* Each SR Traffic Info is of type uint32_t */
43 /* To insturct Coexistence Manager to collect and post SR traffic information */
61 /* To post SR traffic information */
66 * struct coex_collect_sr_traffic_info - Message from CD to CM to request SR traffic info.
70 * Message from CD to CM to request SR traffic information.
171 * struct coex_sr_traffic_info - Message from CM to CD to post SR traffic information.
173 * @sr_traffic_info: Traffic information buffer.
175 * Message from CM to CD to post SR traffic inforamtion
|
| /Zephyr-latest/tests/bsim/bluetooth/mesh/tests_scripts/bridge/ |
| D | brg_table_state_change.sh | 15 # 5. Tester adds an entry to the bridging table to bridge traffic in one direction from tester to
19 # 9. Tester adds a reverse entry to the bridging table to bridge traffic in the other direction from
24 # entry to bridge traffic in the both directions between tester and device 1.
|
| /Zephyr-latest/drivers/ethernet/ |
| D | Kconfig.sam_gmac | 39 bool "Force all traffic to be routed through a specific queue"
44 traffic to be routed through a specific hardware queue. With this enabled
46 This works only if there are four or fewer RX traffic classes enabled, as
47 the SAM GMAC hardware supports screening up to four traffic classes.
|
| /Zephyr-latest/doc/connectivity/networking/ |
| D | network_monitoring.rst | 3 Monitor Network Traffic
10 It is useful to be able to monitor the network traffic especially when
12 Zephyr. This page describes how to set up a way to capture network traffic so
23 network RX and TX traffic. Similar instructions should work also in other
195 The ``2`` tells the network interface which traffic we want to capture. In
197 Note that we send the network traffic to the same interface that we are
199 captured network traffic as that would lead to recursion.
201 Note that you cannot capture traffic from the tunnel interface as that would
203 The captured network traffic can be sent to some other network interface
241 captured network traffic in a useful way.
|
| D | net_config_guide.rst | 79 5-tuple that is used when listening or sending network traffic. Each BSD socket in the
227 Traffic Class Options
230 It is possible to configure multiple traffic classes (queues) when receiving
231 or sending network data. Each traffic class queue is implemented as a thread
236 using a dedicated traffic class thread. This is why by default the
238 not enabled. If userspace is enabled, then the minimum TX traffic class
242 In receiving side, it is recommended to have at least one receiving traffic
246 the packet to the traffic class queue. If the network device driver is not
247 running in IRQ context when it gets the packet, then the RX traffic class
|
| /Zephyr-latest/samples/net/sockets/echo_server/ |
| D | overlay-802154.conf | 3 # Disable TCP and IPv4 (TCP disabled to avoid heavy traffic)
|
| D | overlay-qemu_802154.conf | 3 # Disable TCP and IPv4 (TCP disabled to avoid heavy traffic)
|
| D | overlay-ot.conf | 3 # Disable TCP and IPv4 (TCP disabled to avoid heavy traffic)
|
| /Zephyr-latest/samples/net/sockets/echo_client/ |
| D | overlay-802154.conf | 3 # Disable TCP and IPv4 (TCP disabled to avoid heavy traffic)
|
| D | overlay-qemu_802154.conf | 3 # Disable TCP and IPv4 (TCP disabled to avoid heavy traffic)
|
| /Zephyr-latest/samples/bluetooth/hci_uart_async/ |
| D | debug.mixin.conf | 15 # This outputs all HCI traffic to a separate RTT channel. Use `btmon
|
| /Zephyr-latest/tests/bsim/net/sockets/echo_test/ |
| D | overlay-802154.conf | 5 # Disable TCP and IPv4 (TCP disabled to avoid heavy traffic)
|
| /Zephyr-latest/subsys/net/lib/capture/ |
| D | Kconfig | 29 network traffic. Each network frame sent or received
39 network traffic.
|
| /Zephyr-latest/drivers/console/ |
| D | Kconfig | 54 handling of traffic that goes through the console logic. The debug
154 if traffic on RTT increases (also from host to device). In case of
155 heavy traffic data can be lost and it may be necessary to increase
162 assumes that RTT session is active. In case of heavy traffic data can
|
| /Zephyr-latest/drivers/espi/ |
| D | Kconfig | 182 bool "OOB host-initiated traffic handling"
185 Enables asynchronous handling for host-initiated OOB traffic.
186 Otherwise OOB traffic is assumed to be always client-initiated.
|
| /Zephyr-latest/subsys/logging/backends/ |
| D | Kconfig.rtt | 78 increased if traffic on RTT increases (also from host to device). In
79 case of heavy traffic data can be lost and it may be necessary to
|
| /Zephyr-latest/include/zephyr/bluetooth/mesh/ |
| D | brg_cfg.h | 38 /** Allowed directions for the bridged traffic (or bridged traffic not allowed) */
|
1234567
