Help¶

Define how many Tx traffic classes (queues) the system should have when sending a network packet. The network packet priority can then be mapped to this traffic class so that higher prioritized packets can be processed before lower prioritized ones. Each queue is handled by a separate thread which will need RAM for stack space. Only increase the value from 1 if you really need this feature. The default value is 1 which means that all the network traffic is handled equally. In this implementation, the higher traffic class value corresponds to lower thread priority.

Direct dependencies¶

!NET_RAW_MODE && NETWORKING

(Includes any dependencies from ifs and menus.)

Default¶

1

Kconfig definition¶

At <Zephyr>/subsys/net/ip/Kconfig:140

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:34 → <Zephyr>/subsys/Kconfig:34 → <Zephyr>/subsys/net/Kconfig:87

Menu path: (Top) → Sub Systems and OS Services → Networking → Link layer and IP networking support → IP stack

config NET_TC_TX_COUNT
    int "How many Tx traffic classes to have for each network device"
    range 1 8
    default 1
    depends on !NET_RAW_MODE && NETWORKING
    help
      Define how many Tx traffic classes (queues) the system should have
      when sending a network packet. The network packet priority can then
      be mapped to this traffic class so that higher prioritized packets
      can be processed before lower prioritized ones. Each queue is handled
      by a separate thread which will need RAM for stack space.
      Only increase the value from 1 if you really need this feature.
      The default value is 1 which means that all the network traffic is
      handled equally. In this implementation, the higher traffic class
      value corresponds to lower thread priority.

(The ‘depends on’ condition includes propagated dependencies from ifs and menus.)