| /dpdk/doc/guides/nics/ |
| H A D | nfp.rst | 13 This document explains how to use DPDK with the Netronome Poll Mode
26 with a specific NFP firmware application. Netronome's NSP ABI
37 **https://github.com/Netronome/nfp-drv-kmods** along with the build
40 NFP PMD needs to be used along with UIO ``igb_uio`` or VFIO (``vfio-pci``)
50 NFP PMD, along with a specific NFP firmware application.
67 the PMD with the VFs if the PF is being used by DPDK, that is, with the NFP PF
69 have a PMD able to work with the PF and VFs at the same time and with the PF
75 a PF is initialized, which was not always true with older DPDK versions.
113 DPDK apps work with ports, and a port is usually a PF or a VF PCI device.
153 netdev driver. Make sure you are working with a kernel with NFP PF support or
[all …]
|
| H A D | avp.rst | 27 mechanism. This provides DPDK applications running in virtual machines with
30 The AVP device implementation is integrated with the QEMU/KVM live-migration
32 to another with minimal packet loss.
67 environment and configured with at least one neutron port defined with a
71 Launching a VM with an AVP type network attachment
74 The following example will launch a VM with three network attachments. The
76 network attachments will have a vif-model of "avp" and may be used with a DPDK
|
| H A D | mlx5.rst | 108 - IPv4/UDP with CVLAN filtering
113 - IPv4/TCP with CVLAN filtering
266 cannot be used in conjunction with MPRQ
372 …Other TCP packets (e.g. with MPLS label) received on Rx queue with LRO enabled, will be received w…
440 - Red color must be with drop action.
1065 be cached, helpful with flow insertion rate.
1172 - Configure boot with ``iommu=pt``.
1267 | Offload | with E-Switch | with NIC |
1410 | Shared Action | with E-Switch | with NIC |
1522 #. Start testpmd with basic parameters::
[all …]
|
| /dpdk/doc/guides/prog_guide/ |
| H A D | gpudev.rst | 7 When mixing networking activity with task processing on a GPU device,
8 there may be the need to put in communication the CPU with the device
13 to create a DPDK mempool with external mbufs having the payload
27 and can be disabled with ``-Ddisable_libs=gpudev``.
64 Later, it's also possible to free that memory with gpudev.
81 Later, it's also possible to unmap that memory with gpudev.
96 Considering an application with some GPU task
98 to move forward with the execution.
100 that can be used by the CPU to communicate with a GPU task.
109 Considering an application with a GPU memory mempool
[all …]
|
| H A D | hash_lib.rst | 35 * Delete entry with key: The key is provided as input. If an entry with the specified key is foun…
37 If no entry with the specified key exists in the hash table, then a negative value is returned
39 * Lookup for entry with key: The key is provided as input. If an entry with the specified key is …
182 Implementation Details (with Extendable Bucket)
187 with a linked list of extra buckets and the key is stored in this linked list.
214 .. table:: Entry distribution measured with an example table with 1024 random entries using jhash a…
238 .. table:: Entry distribution measured with an example table with 1 million random entries using jh…
259 utilization with random keys and using Jenkins hash function.
268 …ification typically have a flow table to manage, with each separate flow having an entry associate…
278 with the hash key size set to the number of bytes in the selected flow key.
[all …]
|
| H A D | switch_representation.rst | 14 Network adapters with multiple physical ports and/or SR-IOV capabilities
33 the DPDK flow API (**rte_flow**), with emphasis on the SR-IOV use case
42 A SF shares PCI level resources with other SFs and/or with its parent PCI
45 Sub function is created on-demand, coexists with VFs. Number of SFs is
183 communication between them, with a number of built-in restrictions.
243 communication ports with VFs (assuming **switchdev** topology)
368 The combination of matching criteria with target endpoints fits well with
386 deemed flexible enough to manage representor traffic only with minor
544 Implicit traffic flow with port representor
766 Associating VF 1 with Physical Port 0
[all …]
|
| /dpdk/doc/guides/platform/ |
| H A D | cnxk.rst | 190 # VFIO enabled with TYPE1 IOMMU at minimum
365 Octets of received packets with out error: 0
366 Received packets with alignment errors: 0
372 Packets received with VLAN header: 0
374 Packets received with unicast DMAC: 0
375 Packets received with multicast DMAC: 0
376 Packets received with broadcast DMAC: 0
379 Packets received with an octet count < 64: 0
380 Packets received with an octet count == 64: 0
414 Total frames sent with VLAN header: 0
[all …]
|
| /dpdk/doc/guides/vdpadevs/ |
| H A D | ifc.rst | 18 with its specific subsystem vendor ID and device ID. To let the device be
26 the driver probe a new container is created for this device, with this
27 container vDPA driver can program DMA remapping table with the VM's memory
42 Enable VF data path with virtio information provided by vhost lib, including
55 To create a vhost port with IFC VF
68 - Compatibility with virtio 0.95 and 1.0.
75 - Platform with IOMMU feature. IFC VF needs address translation service to
76 Rx/Tx directly with virtio driver in VM.
86 is mapped to a callfd associated with a virtio ring. Currently only vfio-pci
89 Live Migration with VIRTIO_NET_F_GUEST_ANNOUNCE
|
| H A D | features_overview.rst | 10 Device can handle packets with partial checksum.
13 Guest can handle packets with partial checksum.
19 Device can handle packets with any GSO type.
28 Device can receive TSO with ECN.
70 Host can advise the guest with its maximum supported MTU.
154 Features marked with "P" are partially supported. Refer to the appropriate
|
| /dpdk/doc/guides/sample_app_ug/ |
| H A D | test_pipeline.rst | 15 * Core A ("RX core") receives traffic from the NIC ports and feeds core B with traffic through SW…
60 The hash tables are pre-populated with 16 million keys.
92 …| 3 | hash-[spec]-8-lru | LRU hash table with 8-byte key size and 16 million | 16 m…
93 … | entries. | hash table with the following key f…
98 … | "Sendto output port", with the output port ind…
111 …| 4 | hash-[spec]-8-ext | Extendable bucket hash table with 8-byte key size | Same…
115 …| 5 | hash-[spec]-16-lru | LRU hash table with 16-byte key size and 16 million | 16 m…
116 … | entries. | table with the following key f…
229 the same input traffic can be used to hit all table entries with uniform distribution,
231 The profile for input traffic is TCP/IPv4 packets with:
[all …]
|
| H A D | l3_forward_access_ctrl.rst | 4 L3 Forwarding with Access Control Sample Application
21 * Access Control List (ACL) rules that block packets with a specific characteristic
58 The trick in how to represent a range with a mask and value is as follows.
60 Set those bits that dynamically changed in mask and value with 0.
61 Set those bits that never changed in the mask with 1, in value with number expected.
64 Therefore, set bit 0 in mask and value with 0, set bits 1-7 in mask with 1, and bits 1-7 in value w…
82 Rules with lower priority will NEVER be returned in any cases.
101 * ACL rule line, which starts with a leading character '@'
103 * Route rule line, which starts with a leading character 'R'
105 * Comment line, which starts with a leading character '#'
[all …]
|
| H A D | ip_reassembly.rst | 8 The application performs L3 forwarding with reassembly for fragmented IPv4 and IPv6 packets.
14 with reassembly for IPv4 and IPv6 fragmented packets.
27 associated with that IPv4 address. Any unmatched packets are forwarded to the originating port.
60 To run the example in linux environment with 2 lcores (2,4) over 2 ports(0,2) with 1 RX queue per l…
91 To run the example in linux environment with 1 lcore (4) over 2 ports(0,2) with 2 RX queues per lco…
119 For example, for the fragmented input IPv4 packet with destination address: 100.10.1.1,
169 Then l3fwd_simple_forward() continues with the code for the packet forwarding decision
181 #. If no entry with such key is found, then try to create a new one by one of two ways:
185 …#. Delete a timed-out entry, free mbufs associated with it mbufs and store a new entry with speci…
187 #. Update the entry with new fragment information and check
[all …]
|
| H A D | l2_forward_crypto.rst | 6 L2 Forwarding with Crypto Sample Application
10 the Data Plane Development Kit (DPDK), in conjunction with the Cryptodev library.
17 with a crypto device capable of doing that operation,
115 * auth_iv: set the auth IV to be used. Bytes has to be separated with ":"
127 * aead_key: set the AEAD key to be used. Bytes has to be separated with ":"
135 * aead_iv: set the AEAD IV to be used. Bytes has to be separated with ":"
141 * aad: set the AAD to be used. Bytes has to be separated with ":"
199 Encryption flow Through the L2 Forwarding with Crypto Application
214 * Encryption with AES-CBC with 128 bit key.
216 * Authentication with SHA1-HMAC (generation).
[all …]
|
| H A D | l3_forward_graph.rst | 25 graph using ``rte_graph_walk()`` with graph objects created one per worker lcore.
72 For example, consider a dual processor socket platform with 8 physical cores, where cores 0-7 and 1…
125 ``ethdev_tx-X`` where X, Y represent port id and queue id associated with them.
129 These cloned nodes along with existing static nodes such as ``ip4_lookup`` and
142 Now a graph needs to be created with a specific set of nodes for every lcore.
145 it can be associated with all the graphs created as all the lcores should have
147 (port, rx_queue_id), so they should be associated with a graph based on
154 found with a given regex node pattern.
186 forwarding data is updated with nodes, worker lcores will be launched with graph
188 continuously call a non-blocking API ``rte_graph_walk()`` with it's lcore
[all …]
|
| H A D | ip_frag.rst | 9 The application does L3 forwarding with IPv4 and IPv6 packet fragmentation.
29 associated with that IP address.
45 The LPM object is created and loaded with the pre-configured entries read from
64 To run the example in linux environment with 2 lcores (2,4) over 2 ports(0,2) with 1 RX queue per l…
93 To run the example in linux environment with 1 lcore (4) over 2 ports(0,2) with 2 RX queues per lco…
116 For example, for the input IPv4 packet with destination address: 100.10.1.1 and packet length 9198 …
|
| H A D | bbdev_app.rst | 21 packet is compared with the baseband operations output. Then it's looped back to
34 DPDK needs to be built with ``baseband_turbo_sw`` PMD enabled along
35 with ``FLEXRAN SDK`` Libraries. Refer to *SW Turbo Poll Mode Driver*
63 To run the application in linux environment with the turbo_sw baseband device
90 Using Packet Generator with baseband device sample application
95 it will print the transmitted along with the looped-back traffic on Rx ports.
115 Pktgen with DPDK applications.
|
| /dpdk/doc/guides/howto/ |
| H A D | rte_flow.rst | 8 with the ``rte_flow`` APIs.
71 Terminal 1: running sample app with the flow rule disabled::
87 received packet with src ip = 176.80.50.4
88 received packet with src ip = 176.80.50.5
106 received packet with src ip = 176.80.50.4
187 received packet with src ip = 176.80.50.4
188 received packet with src ip = 176.80.50.5
189 received packet with src ip = 176.80.50.6
209 received packet with src ip = 176.80.50.6
281 received packet with src ip = 176.80.50.4 sent to queue 2
[all …]
|
| H A D | virtio_user_for_container_networking.rst | 26 The virtual device, virtio-user, with unmodified vhost-user backend, is designed
56 Here we use Docker as container engine. It also applies to LXC, Rocket with
76 #. Start a testpmd on the host with a vhost-user port.
84 #. Start a container instance with a virtio-user port.
101 * Cannot work with --huge-unlink option. As we need to reopen the hugepage
102 file to share with vhost backend.
103 * Cannot work with --no-huge option. Currently, DPDK uses anonymous mapping
104 under this option which cannot be reopened to share with vhost backend.
109 will bring confusion when sharing hugepage files with backend by name.
|
| H A D | virtio_user_as_exceptional_path.rst | 9 The virtual device, virtio-user, was originally introduced with vhost-user
13 Virtio_user with vhost-kernel backend is a solution for exceptional path,
14 such as KNI which exchanges packets with kernel networking stack. This
52 This physical NIC is for communicating with outside.
63 This command runs testpmd with two ports, one physical NIC to communicate
64 with outside, and one virtio-user to communicate with kernel.
|
| /dpdk/doc/guides/contributing/ |
| H A D | abi_policy.rst | 17 with the major ABI version is mandatory in subsequent releases until a
19 #. Major ABI versions are usually but not always declared aligned with a
26 symbols is managed with :ref:`ABI Versioning <abi_versioning>`.
167 API becomes non-experimental, then the old one is marked with
175 compatibility with the last major ABI version is then dropped.
178 with the original contributor of the ABI changes, failing that, then with
179 the contributor's company and then finally with the maintainer.
211 changes, however with the following additional requirements:
266 22, to be replaced with the inline function ``rte_foo()``.
293 A new ABI version may be declared aligned with a given release.
[all …]
|
| /dpdk/doc/guides/tools/ |
| H A D | flow-perf.rst | 57 with a ``--`` separator:
166 under ``VNI_VALUE`` with full mask, default value = 1.
171 This item have incremental source IP, with full mask.
176 This item have incremental source IP, with full mask.
188 under ``VNI_VALUE`` with full mask, default value = 1.
194 under ``VNI_VALUE`` with full mask, default value = 1.
246 the same with number of set bits in portmask.
258 The app running with 4 RX queues
282 with full mask, default value = 1.
287 with full mask, default value = 1.
[all …]
|
| /dpdk/doc/guides/rel_notes/ |
| H A D | release_20_05.rst | 26 These APIs help an application use lock-free data structures with
98 Updated i40e PMD with new features and improvements, including:
109 * Added advanced iavf with FDIR capability.
124 * Hierarchical Scheduling with DWRR and SP.
148 * Updated the AESNI MB PMD with AES-256 DOCSIS algorithm.
301 Added support for building with GCC 10.1.
321 * Intel\ |reg| platforms with Broadcom\ |reg| NICs combinations
371 * Intel\ |reg| platforms with Intel\ |reg| NICs combinations
478 * Intel\ |reg| platforms with Mellanox\ |reg| NICs combinations
568 * IBM Power 9 platforms with Mellanox\ |reg| NICs combinations
[all …]
|
| H A D | release_20_02.rst | 19 New APIs have been added to support rings with custom element size.
21 * **Added mbuf pool with pinned external memory.**
57 * Added support for MAC/VLAN with TCP/UDP in switch rule.
63 Updated iavf PMD with new features and improvements, including:
70 Updated ixgbe PMD with new features and improvements, including:
78 Updated i40e PMD with new features and improvements, including:
97 * Added support for the mbufs with external pinned buffers.
254 * Intel\ |reg| platforms with Intel\ |reg| NICs combinations
361 * Intel\ |reg| platforms with Mellanox\ |reg| NICs combinations
460 * IBM Power 9 platforms with Mellanox\ |reg| NICs combinations
[all …]
|
| /dpdk/license/ |
| H A D | lgpl-2.1.txt | 43 code. If you link other code with the library, you must provide
113 be combined with the library in order to run.
155 warranty; and distribute a copy of this License along with the
207 with the Library (or with a work based on the Library) on a volume of
238 compelled to copy the source along with the object code.
286 a) Accompany the work with the complete corresponding
290 with the Library, with the complete machine-readable "work that
304 interface-compatible with the version that the work was made with.
306 c) Accompany the work with a written offer, valid for at
341 based on the Library, uncombined with any other library
[all …]
|
| H A D | README | 5 source code with mostly redundant information. An additional problem
8 indentation, line wrapping and/or white space, with obsolete address
33 To label a file as dual-licensed with BSD-3-Clause and GPL-2.0 (e.g., for code
39 To label a file as dual-licensed with BSD-3-Clause and LGPL-2.1 (e.g., for code
47 with SPDX-License-Identifiers.
57 mission, it may decide on such exception with two-thirds vote of the members.
61 Any approvals shall be documented in "Licenses/exceptions.txt" with record
|