Lines Matching refs:kernel

8 allows userspace applications to exchange packets with the kernel networking stack.
10 to request the creation of a KNI virtual device in the Linux* kernel.
12 which is re-mapped into the kernel address space by the KNI kernel loadable module
15 to the kernel module for each device allocated.
17 The KNI kernel loadable module is a standard net driver,
22 *   Provides a faster mechanism to interface with the kernel net stack and eliminates system calls
29 of the DPDK to create a path for packets to go through the Linux* kernel.
30 This is done by creating one or more kernel net devices for each of the DPDK ports.
32 also the exchange of packets between the DPDK application and the Linux* kernel.
35 KNI kernel module ``rte_kni`` be loaded into the kernel.  See
37 the ``rte_kni`` kernel module.
69 If link monitoring is enabled, the ``rte_kni`` kernel module should be loaded
74 If link monitoring is not enabled, the ``rte_kni`` kernel module should be
110     the KNI kernel thread(s) are bound to for each physical port.
135 cores are used to pin the kernel threads in the ``rte_kni`` kernel module.
145 be created for the physical port ``port`` and the KNI kernel thread(s)
150 ``port``.  If the ``rte_kni`` kernel module is loaded in :ref:`multiple
151 kernel thread <kni_kernel_thread_mode>` mode, a kernel thread will be created
153 kernel module is loaded in :ref:`single kernel thread <kni_kernel_thread_mode>`
154 mode, only one kernel thread is started for all KNI interfaces.  The kernel
160 The following commands will first load the ``rte_kni`` kernel module in
161 :ref:`multiple kernel thread <kni_kernel_thread_mode>` mode.  The ``kni``
164 ``vEth0_0`` with the kernel thread bound to lcore 8.  Port 1 uses lcore
166 interface ``vEth1_0`` with the kernel thread bound to lcore 9.
171     # insmod <build_dir>/kernel/linux/kni/rte_kni.ko kthread_mode=multiple
179 The kernel thread for each interface will be bound as follows:
189     # insmod <build_dir>/kernel/linux/kni/rte_kni.ko kthread_mode=multiple
193 test application and the ``rte_kni`` kernel module.  In this example,
194 the ``rte_kni`` kernel module is loaded in :ref:`single kernel thread
200 created for port 1.  Since ``rte_kni`` is loaded in "single kernel thread"
201 mode, the one kernel thread is bound to lcore 8.
209     # insmod <build_dir>/kernel/linux/kni/rte_kni.ko lo_mode=lo_mode_fifo carrier=on
272 from the Linux kernel.
283 In addition, one or more kernel NIC interfaces are allocated for each
286 The code for allocating the kernel NIC interfaces for a specific port is
290 is the association of each port with lcores for RX, TX and kernel threads.
296 *   Other lcores for pinning the kernel threads on one by one
306 to see if this lcore is reading from or writing to kernel NIC interfaces.
308 For the case that reads from a NIC port and writes to the kernel NIC interfaces (``kni_ingress``),
311 The packet transmission is done by sending mbufs into the kernel NIC interfaces by ``rte_kni_tx_bur…
312 The KNI library automatically frees the mbufs after the kernel successfully copied the mbufs.
314 For the other case that reads from kernel NIC interfaces
316 packets are retrieved by reading mbufs from kernel NIC interfaces by ``rte_kni_rx_burst()``.