Lines Matching refs:interface

11 The IOCTL call provides interface information and the DPDK's physical address space,
22 *   Provides a faster mechanism to interface with the kernel net stack and eliminates system calls
48 It is recommended to configure one KNI interface for each physical NIC port.
49 The application can be configured with more than one KNI interface for
65 KNI interface(s) to match the physical NIC port's state.  This means that
66 the KNI interface(s) will be disabled automatically when the Ethernet link
71 set to *off*.  This ensures that the KNI interface is only enabled *after*
125     network interface to match it.  This means that the KNI interface will
144 If no lcore ID is specified for ``lcore_kthread``, one KNI interface will
148 If one or more lcore IDs are specified for ``lcore_kthread``, a KNI interface
152 for each KNI interface and bound to the specified core.  If the ``rte_kni``
163 Rx task, lcore 6 for the Tx task, and will create a single KNI interface
166 interface ``vEth1_0`` with the kernel thread bound to lcore 9.
179 The kernel thread for each interface will be bound as follows:
192 The following example can be used to test the interface between the ``kni``
198 to be connected in order to use the KNI interface.  One KNI interface
199 ``vEth0_0`` is created for port 0 and one KNI interface ``vEth1_0`` is
217 Linux network interface.
219 Enable KNI interface and assign an IP address:
225 Show KNI interface configuration and statistics:
249 MTU size used by the physical NIC which corresponds to the KNI interface.
250 However, if more than one KNI interface is configured for a physical port,
251 these commands will only work on the first KNI interface for that port.