The ``lo_mode_fifo_skb`` loopback option will loop back ring enqueue/dequeue
operations and sk buffer copies in kernel space.
The ``lo_mode_fifo_skb`` loopback option will loop back ring enqueue/dequeue
operations and sk buffer copies in kernel space.
This mode will create only one kernel thread for all KNI interfaces to
receive data on the kernel side. By default, this kernel thread is not
This mode will create only one kernel thread for all KNI interfaces to
receive data on the kernel side. By default, this kernel thread is not
This mode will create a separate kernel thread for each KNI interface to
receive data on the kernel side. The core affinity of each ``kni_thread``
This mode will create a separate kernel thread for each KNI interface to
receive data on the kernel side. The core affinity of each ``kni_thread``
If the ``carrier`` parameter is not specified, the default carrier state
of KNI interfaces will be set to *off*.
If the ``carrier`` parameter is not specified, the default carrier state
of KNI interfaces will be set to *off*.
-------------------------
Before any KNI interfaces can be created, the ``rte_kni`` kernel module must
-------------------------
Before any KNI interfaces can be created, the ``rte_kni`` kernel module must
The KNI interfaces are created by a DPDK application dynamically via the
``rte_kni_alloc()`` function.
The KNI interfaces are created by a DPDK application dynamically via the
``rte_kni_alloc()`` function.
The current version of kni provides minimal ethtool functionality
including querying version and link state. It does not support link
control, statistics, or dumping device registers.
The current version of kni provides minimal ethtool functionality
including querying version and link state. It does not support link
control, statistics, or dumping device registers.