Lines Matching refs:kernel

18 *   Allows an interface with the kernel network stack.
32 The KNI kernel loadable module ``rte_kni`` provides the kernel interface
37 the kernel module.
39 The ``rte_kni`` kernel module contains several optional parameters which
48                     lo_mode_fifo        Enable kernel loopback with fifo
49                     lo_mode_fifo_skb    Enable kernel loopback with fifo and skb buffer
52                     single    Single kernel thread mode enabled.
53                     multiple  Multiple kernel thread mode enabled.
60 Loading the ``rte_kni`` kernel module without any optional parameters is
61 the typical way a DPDK application gets packets into and out of the kernel
62 network stack.  Without any parameters, only one kernel thread is created
63 for all KNI devices for packet receiving in kernel side, loopback mode is
68     # insmod <build_dir>/kernel/linux/kni/rte_kni.ko
75 For testing, the ``rte_kni`` kernel module can be loaded in loopback mode
80     # insmod <build_dir>/kernel/linux/kni/rte_kni.ko lo_mode=lo_mode_fifo
83 operations in kernel space.
87     # insmod <build_dir>/kernel/linux/kni/rte_kni.ko lo_mode=lo_mode_fifo_skb
90 operations and sk buffer copies in kernel space.
99 To provide flexibility of performance, the ``rte_kni`` KNI kernel module
100 can be loaded with the ``kthread_mode`` parameter.  The ``rte_kni`` kernel
101 module supports two options: "single kernel thread" mode and "multiple
102 kernel thread" mode.
104 Single kernel thread mode is enabled as follows:
108     # insmod <build_dir>/kernel/linux/kni/rte_kni.ko kthread_mode=single
110 This mode will create only one kernel thread for all KNI interfaces to
111 receive data on the kernel side.  By default, this kernel thread is not
113 this kernel thread by setting the ``core_id`` and ``force_bind`` parameters
116 For optimum performance, the kernel thread should be bound to a core in
119 The KNI kernel module can also be configured to start a separate kernel
121 kernel thread mode is enabled as follows:
125     # insmod <build_dir>/kernel/linux/kni/rte_kni.ko kthread_mode=multiple
127 This mode will create a separate kernel thread for each KNI interface to
128 receive data on the kernel side.  The core affinity of each ``kni_thread``
129 kernel thread can be specified by setting the ``core_id`` and ``force_bind``
132 Multiple kernel thread mode can provide scalable higher performance if
135 If the ``kthread_mode`` parameter is not specified, the "single kernel
144 kernel module is controlled via the ``carrier`` option when the module
147 If ``carrier=off`` is specified, the kernel module will leave the carrier
154 If ``carrier=on`` is specified, the kernel module will automatically set
166     # insmod <build_dir>/kernel/linux/kni/rte_kni.ko carrier=on
172     # insmod <build_dir>/kernel/linux/kni/rte_kni.ko carrier=off
180 Before any KNI interfaces can be created, the ``rte_kni`` kernel module must
181 be loaded into the kernel and configured with the ``rte_kni_init()`` function.
188 random MAC address and control the affinity of the kernel Rx thread(s)
194 handle requests from the ``rte_kni`` kernel module.  These functions
263 To minimize the amount of DPDK code running in kernel space, the mbuf mempool is managed in userspa…
264 The kernel module will be aware of mbufs,
289 in different hugepage segments from causing kernel crash.
294 …s the DPDK application must first enqueue several mbufs to create an mbuf cache on the kernel side.
320 Ethtool is a Linux-specific tool with corresponding support in the kernel.