| /dpdk/doc/guides/howto/ |
| H A D | rte_flow.rst | 76 Terminal 2: running scapy:: 90 Terminal 1: running sample the app flow rule enabled:: 95 Terminal 2: running scapy:: 169 Terminal 1: running sample app flow rule disabled:: 174 Terminal 2: running scapy:: 191 Terminal 1: running sample app flow rule enabled:: 196 Terminal 2: running scapy:: 263 Terminal 1: running sample app flow rule disabled:: 268 Terminal 2: running scapy:: 285 Terminal 1: running sample app flow rule enabled:: [all …]
|
| H A D | debug_troubleshoot.rst | 34 primary process, with various processing stages running on multiple cores. The 257 * Ensure cryptodev, resources and enqueue is running on NUMA cores. 265 * Ensure cryptodev, resources and dequeue are running on NUMA cores. 299 * The functions running on CPU cores without context switches are the 303 * Use ``rte_thread_get_affinity`` to isolate functions running on the same 312 * For high-performance execution logic ensure running it on correct NUMA 330 functions running on service cores 349 * Check if service is running with ``rte_service_runstate_get``.
|
| H A D | lm_virtio_vhost_user.rst | 4 Live Migration of VM with Virtio on host running vhost_user 11 running the Vhost sample application (vhost-switch) and using the DPDK PMD (ixgbe or i40e). 23 QEMU 2.5 is required for Live Migration of a VM with vhost_user running on the hosts. 237 VM status: running
|
| /dpdk/doc/guides/sample_app_ug/ |
| H A D | pipeline.rst | 43 * Argument: IP Address of the host running the application to be used by 52 * Argument: TCP port number at which the application is running. 55 Refer to *DPDK Getting Started Guide* for general information on running applications and the Envir… 81 When running a telnet client as above, command prompt is displayed: 93 Once application and telnet client start running, messages can be sent from client to application.
|
| H A D | service_cores.rst | 83 Note that it is not allowed to remove a service core if the service is running, 84 and the service-core is the only core running that service (see documentation 95 method of registering functions to be run, allowing the running of the
|
| H A D | bbdev_app.rst | 64 using the allow option for pci device running on 1 encoding lcore and 1 decoding lcore 87 Refer to the *DPDK Getting Started Guide* for general information on running 114 Refer to *The Pktgen Application* documents for general information on running
|
| H A D | vmdq_forwarding.rst | 38 To have the application display the statistics, send a SIGHUP signal to the running application pro… 61 Refer to the *DPDK Getting Started Guide* for general information on running applications and 129 Please note that the statistics output will appear on the terminal where the vmdq_app is running,
|
| H A D | vdpa.rst | 36 * --client means running vdpa app in client mode, in the client mode, QEMU needs 60 and we need to bind vfio-pci to them before running vdpa sample.
|
| /dpdk/doc/guides/prog_guide/ |
| H A D | intro.rst | 10 For programming examples and for instructions on compiling and running each sample application, 13 For general information on compiling and running applications, see the *DPDK Getting Started Guide*. 25 designed to get users up and running quickly with the software.
|
| H A D | service_cores.rst | 14 running services). The power of the service core concept is that the mapping 41 lcore in question from running the service. 54 profile the services running on the system at any time.
|
| H A D | multi_proc_support.rst | 78 whereby a DPDK process is started as a secondary instance if a primary instance is already running. 87 This model is equivalent to having multiple threads each running the same main-loop function, 133 …Independent DPDK instances running side-by-side on a single machine cannot share any network ports. 140 this can be trivially extended to multi-process groups of DPDK applications running side-by-side. 146 All restrictions and issues with multiple independent DPDK processes running side-by-side 152 There are a number of limitations to what can be done when running DPDK multi-process applications. 167 * All DPDK processes running as a single application and using shared memory must have distinct c… 177 * The use of function pointers between multiple processes running based of different compiled bin…
|
| /dpdk/drivers/dma/skeleton/ |
| H A D | skeleton_dmadev.c | 168 struct rte_ring *running; in vchan_setup() local 184 running = rte_ring_create("dma_skeleton_desc_running", nb_desc, in vchan_setup() 188 if (empty == NULL || pending == NULL || running == NULL || in vchan_setup() 193 rte_ring_free(running); in vchan_setup() 209 hw->desc_running = running; in vchan_setup()
|
| /dpdk/doc/guides/linux_gsg/ |
| H A D | enable_func.rst | 24 When running as non-root user, there may be some additional resource limits 38 resources also should be accessible by the user running the DPDK application. 50 The instructions below will allow running DPDK with ``igb_uio`` or 94 To help prevent additional workloads from running on those cores,
|
| H A D | intro.rst | 8 It is designed to get customers up and running quickly. 20 …ibes how to install and configure the DPDK; designed to get users up and running quickly with the …
|
| H A D | build_sample_apps.rst | 20 Before running the application make sure: 115 and that cores 0-3 are present and are to be used for running the application):: 121 The ``--proc-type`` and ``--file-prefix`` EAL options are used for running 135 …s on the system by examining the ``/proc/cpuinfo`` file, for example, by running cat ``/proc/cpuin… 159 When running an application, it is recommended to use the same amount of memory as that allocated f…
|
| H A D | linux_eal_parameters.rst | 8 used by any DPDK application running on Linux. 53 allows running multiple independent DPDK primary/secondary processes under
|
| /dpdk/doc/guides/freebsd_gsg/ |
| H A D | build_sample_apps.rst | 52 #. The ``contigmem`` and ``nic_uio`` modules must be set up prior to running an application. 55 as described in section :ref:`binding_network_ports`, prior to running the application. 60 A large number of options can be given to the EAL when running an
|
| H A D | freebsd_eal_parameters.rst | 8 used by any DPDK application running on FreeBSD.
|
| H A D | intro.rst | 9 up and running quickly and describes how to compile and run a 33 configure the DPDK; designed to get users up and running quickly with the
|
| /dpdk/doc/guides/nics/ |
| H A D | vdev_netvsc.rst | 10 Linux virtual machines running on Microsoft Hyper-V_ (including Azure) 90 If nonzero, ignores the driver running (actually used to disable the
|
| H A D | avp.rst | 27 mechanism. This provides DPDK applications running in virtual machines with 66 * A virtual machine running in a Wind River Systems virtualization
|
| /dpdk/doc/guides/windows_gsg/ |
| H A D | run_apps.rst | 11 ``SeLockMemoryPrivilege`` for the user running an application. 73 The list can be extended in order to try running DPDK with new devices.
|
| /dpdk/doc/guides/cryptodevs/ |
| H A D | octeontx.rst | 123 The symmetric crypto operations on OCTEON TX crypto PMD may be verified by running the test 131 The asymmetric crypto operations on OCTEON TX crypto PMD may be verified by running the test
|
| H A D | ccp.rst | 73 Bind the CCP devices to DPDK UIO driver module before running the CCP PMD stack. 95 (by default, socket_id will be the socket where the core that is creating the PMD is running on).
|
| /dpdk/doc/guides/regexdevs/ |
| H A D | mlx5.rst | 43 - BlueField-2 running Mellanox supported kernel.
|