| /dpdk/lib/cryptodev/ |
| H A D | cryptodev_trace_points.c | 25 lib.cryptodev.sym.pool.create) 28 lib.cryptodev.asym.pool.create) 31 lib.cryptodev.sym.create) 34 lib.cryptodev.asym.create)
|
| /dpdk/doc/guides/howto/ |
| H A D | rte_flow.rst | 22 In this example we will create a simple rule that drops packets whose IPv4 26 testpmd> flow create 0 ingress pattern eth / vlan / 34 /* create the attribute structure */ 60 /* create the drop action */ 64 /* validate and create the flow rule */ 121 testpmd> flow create 0 ingress pattern eth / vlan / 158 /* create the drop action */ 162 /* validate and create the flow rule */ 222 testpmd> flow create 0 ingress pattern eth / vlan vid spec 123 / 251 /* create the queue action */ [all …]
|
| /dpdk/doc/guides/sample_app_ug/ |
| H A D | ip_pipeline.rst | 15 to create complete applications (super-pipelines). 148 …| L2fwd | Stub | Forward | 1. Mempool create … 149 …| | | | 2. Link create … 150 …| Note: Implemented | | | 3. Pipeline create … 157 …| Flow classification | Exact match | Forward | 1. Mempool create … 158 …| | | | 2. Link create … 159 …| | * Key = byte array | | 3. Pipeline create … 167 …| KNI | Stub | Forward | 1. Mempool create … 168 …| | | | 2. Link create … 169 …| | | | 3. Pipeline create … [all …]
|
| H A D | vdpa.rst | 46 3. create: create a new vdpa port with socket file and vdpa device address 65 Then we can create 2 vdpa ports in interactive cmdline. 75 vdpa> create /tmp/vdpa-socket0 0000:06:00.3 76 vdpa> create /tmp/vdpa-socket1 0000:06:00.4
|
| H A D | flow_filtering.rst | 132 In the next step we create and apply the flow rule. which is to send packets 139 :end-before: >8 End of create flow and the flow rule. 203 The following part create the flow attributes, in our case ingress. 247 The last part of the function is to validate the rule and create it. 251 :start-after: Validate the rule and create it. 8< 252 :end-before: >8 End of validation the rule and create it.
|
| /dpdk/lib/eventdev/ |
| H A D | eventdev_trace_points.c | 45 lib.eventdev.rx.adapter.create) 64 lib.eventdev.tx.adapter.create) 86 lib.eventdev.timer.create) 108 lib.eventdev.crypto.create)
|
| /dpdk/doc/guides/testpmd_app_ug/ |
| H A D | testpmd_funcs.rst | 2512 create bonded device 2521 testpmd> create bonded device 1 0 2800 create port policy 2824 create port meter 3369 flow table {port_id} create 3389 flow queue {port_id} create {queue_id} 3411 flow create {port_id} 3449 - Tunnel offload - create a tunnel stub:: 3593 flow template_table {port_id} create 3732 flow create {port_id} [all …]
|
| /dpdk/doc/guides/nics/ |
| H A D | axgbe.rst | 65 USER1: create a new mbuf pool <mbuf_pool_socket_0>: n=171456, size=2176, socket=0 66 USER1: create a new mbuf pool <mbuf_pool_socket_1>: n=171456, size=2176, socket=1 67 USER1: create a new mbuf pool <mbuf_pool_socket_2>: n=171456, size=2176, socket=2 68 USER1: create a new mbuf pool <mbuf_pool_socket_3>: n=171456, size=2176, socket=3
|
| H A D | kni.rst | 15 To create a KNI device ``net_kni#`` device name should be used, and this 16 will create ``kni#`` Linux virtual network interface. 25 an application should control a physical port and create one virtual KNI port, 34 EAL ``--vdev`` argument can be used to create KNI device instance, like:: 38 Above command will create ``kni0`` and ``kni1`` Linux network interfaces, 50 ``librte_kni`` can create Linux network interfaces with different features,
|
| H A D | memif.rst | 29 ``--vdev=net_memif1`` option given will create an interface named net_memif0, 53 In order to create memif connection, two memif interfaces, each in separate 70 listening on this socket will extract the connection request and create a new 188 Instead of using memfd_create() to create new shared file, existing memsegs are used. 215 First create ``server`` interface:: 219 Now create ``client`` interface (server must be already running so the client will connect):: 247 vpp# create interface memif id 0 server no-zero-copy 259 Now create memif interface by running testpmd with these command line options:: 263 Testpmd should now create memif client interface and try to connect to server. 279 In this example we will create 2 memif ports connected into loopback.
|
| H A D | igc.rst | 88 testpmd> flow create 0 ingress pattern eth type is 0x801 / end actions queue index 1 / end 94 …testpmd> flow create 0 ingress pattern eth / ipv4 proto is 6 / tcp dst is 0x80 / end actions queue… 106 testpmd> flow create 0 ingress pattern end actions rss types ipv4-udp end / end
|
| H A D | tap.rst | 14 create a number of tap devices in the host accessed via ``ifconfig -a`` or 22 ``--vdev=net_tap1`` option given will create an interface named dtap0, dtap1, 31 Using the option ``mac=fixed`` you can create a fixed known MAC address:: 86 The TUN PMD allows user to create a TUN device on host. The PMD allows user 137 testpmd> flow create 0 priority 1 ingress pattern eth / ipv4 dst is 192.0.2.1 \ 142 testpmd> flow create 0 priority 2 ingress pattern eth src is 06:05:04:03:02:01 \ 147 testpmd> flow create 0 priority 3 ingress pattern eth / vlan vid is 3 / \ 152 testpmd> flow create 0 priority 4 ingress pattern eth dst is 0a:0b:0c:0d:0e:0f \ 209 Then use socat to create a loopback for the two interfaces::
|
| H A D | hns3.rst | 191 testpmd> flow create 0 ingress pattern eth / ipv4 src is 2.2.2.3 \ 207 testpmd> flow create 0 ingress pattern end actions rss types end \ 214 testpmd> flow create 0 ingress pattern eth / ipv4 / tcp / end \ 221 testpmd> flow create 0 ingress pattern eth / ipv4 / tcp / end \ 228 testpmd> flow create 0 ingress pattern end actions rss types end \
|
| H A D | dpaa2.rst | 44 network ports to create functional objects/devices such as network 61 | (create,discover,connect 87 The MC mediates operations such as create, discover, 152 that can be used to create/destroy containers and objects 383 create a hardware offloaded packet buffer mempool. 649 flow create 1 group 0 priority 1 ingress pattern ipv4 src is \ 651 flow create 1 group 0 priority 2 ingress pattern ipv4 src is \ 653 flow create 1 group 0 priority 3 ingress pattern ipv4 src is \ 655 flow create 1 group 0 priority 4 ingress pattern ipv4 src is \
|
| /dpdk/lib/port/ |
| H A D | rte_swx_port.h | 102 rte_swx_port_in_create_t create; member 183 rte_swx_port_out_create_t create; member
|
| H A D | rte_swx_port_source_sink.c | 205 .create = source_create, 214 .create = NULL, 337 .create = sink_create,
|
| H A D | rte_swx_port_fd.c | 286 .create = reader_create, 293 .create = writer_create,
|
| /dpdk/lib/mempool/ |
| H A D | mempool_trace_points.c | 34 lib.mempool.create) 37 lib.mempool.create.empty)
|
| /dpdk/doc/guides/prog_guide/ |
| H A D | graph_lib.rst | 8 ``links`` them together to create a complex ``graph`` to enable reusable/modular 12 create, lookup, dump and destroy on graph and node operations such as clone, 13 edge update, and edge shrink, etc. The API also allows to create the stats 135 Link the Nodes to create the graph topology 144 functions can links them together to create a complex packet processing graph. 157 to update the ``next_nodes[]`` links for the node runtime but before graph create. 174 Now that the nodes are linked, Its time to create a graph by including 177 matching to include the required nodes. After the graph create any changes to 180 The ``rte_graph_create()`` API shall be used to create the graph. 198 processing strategy would be to create graph object PER WORKER.
|
| H A D | switch_representation.rst | 518 testpmd> flow create 3 ingress pattern vf id is 1 / end 781 flow create 3 ingress 787 flow create 4 ingress 799 flow create 3 ingress 810 flow create 3 egress 818 flow create 4 ingress 822 flow create 5 ingress 836 flow create 5 ingress 842 flow create 5 egress 855 flow create 5 ingress [all …]
|
| H A D | overview.rst | 22 Once the EAL library is created, the user may link with the library to create their own application… 42 editor and various libraries to create the DPDK components and libraries. 45 they may then be used to create the user's data plane application. 121 The mbuf library provides the facility to create and destroy buffers
|
| /dpdk/lib/eal/linux/ |
| H A D | eal_vfio.c | 1721 struct vfio_iommu_spapr_tce_create create = { in vfio_spapr_create_dma_window() local 1722 .argsz = sizeof(create), }; in vfio_spapr_create_dma_window() 1751 create.window_size = spapr_dma_win_len; in vfio_spapr_create_dma_window() 1752 create.page_shift = __builtin_ctzll(spapr_dma_win_page_sz); in vfio_spapr_create_dma_window() 1753 create.levels = 1; in vfio_spapr_create_dma_window() 1754 ret = ioctl(vfio_container_fd, VFIO_IOMMU_SPAPR_TCE_CREATE, &create); in vfio_spapr_create_dma_window() 1767 for (levels = create.levels + 1; in vfio_spapr_create_dma_window() 1769 create.levels = levels; in vfio_spapr_create_dma_window() 1771 VFIO_IOMMU_SPAPR_TCE_CREATE, &create); in vfio_spapr_create_dma_window() 1784 if (create.start_addr != 0) { in vfio_spapr_create_dma_window() [all …]
|
| /dpdk/lib/table/ |
| H A D | rte_swx_table.h | 275 rte_swx_table_create_t create; member
|
| /dpdk/examples/pipeline/examples/ |
| H A D | l2fwd_pcap.cli | 6 pipeline PIPELINE0 create 0
|
| H A D | l2fwd_macswp_pcap.cli | 6 pipeline PIPELINE0 create 0
|