Lines Matching refs:thread

51     parm:           kthread_mode: Kernel thread mode (default=single):
52                     single    Single kernel thread mode enabled.
53                     multiple  Multiple kernel thread mode enabled.
64 …parm:           min_scheduling_interval: KNI thread min scheduling interval (default=100 microseco…
66 …parm:           max_scheduling_interval: KNI thread max scheduling interval (default=200 microseco…
72 network stack.  Without any parameters, only one kernel thread is created
111 module supports two options: "single kernel thread" mode and "multiple
112 kernel thread" mode.
114 Single kernel thread mode is enabled as follows:
120 This mode will create only one kernel thread for all KNI interfaces to
121 receive data on the kernel side.  By default, this kernel thread is not
123 this kernel thread by setting the ``core_id`` and ``force_bind`` parameters
126 For optimum performance, the kernel thread should be bound to a core in
130 thread for each KNI interface created by the DPDK application.  Multiple
131 kernel thread mode is enabled as follows:
137 This mode will create a separate kernel thread for each KNI interface to
139 kernel thread can be specified by setting the ``core_id`` and ``force_bind``
142 Multiple kernel thread mode can provide scalable higher performance if
146 thread" mode is used.
249 random MAC address and control the affinity of the kernel Rx thread(s)
313 to create a separate thread or secondary process to periodically call
340 On the DPDK RX side, the mbuf is allocated by the PMD in the RX thread context.
341 This thread will enqueue the mbuf in the rx_q FIFO,
343 The KNI thread will poll all KNI active devices for the rx_q.
348 The RX thread, in the same main loop, polls this FIFO and frees the mbuf after dequeuing it.
361 The DPDK TX thread dequeues the mbuf and sends it to the PMD via ``rte_eth_tx_burst()``.