| /dpdk/drivers/net/mlx5/linux/ |
| H A D | mlx5_vlan_os.c | 42 MLX5_ASSERT(vlan->created); in mlx5_vlan_vmwa_release()
44 if (!vlan->created || !vmwa) in mlx5_vlan_vmwa_release()
46 vlan->created = 0; in mlx5_vlan_vmwa_release()
73 MLX5_ASSERT(!vlan->created); in mlx5_vlan_vmwa_acquire()
75 if (vlan->created || !vmwa) in mlx5_vlan_vmwa_acquire()
86 vlan->created = 1; in mlx5_vlan_vmwa_acquire()
|
| /dpdk/doc/guides/sample_app_ug/ |
| H A D | l3_forward_graph.rst | 25 graph using ``rte_graph_walk()`` with graph objects created one per worker lcore.
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
146 Tx capability for every port. But ``ethdev_rx-X-Y`` node is created per
165 Once graph objects are created, node specific info like routes and rewrite
189 specific graph object that was already created.
|
| H A D | l2_forward_crypto.rst | 149 * sessionless: no crypto session will be created.
162 a SW crypto device/s (virtual crypto PMD) must be created (using --vdev).
242 or created using the EAL option --vdev (if they are virtual devices),
284 This session is created and is later attached to the crypto operation:
288 :start-after: Session is created and is later attached to the crypto operation. 8<
314 Once the operation has been created, it has to be enqueued in one of the crypto devices.
|
| H A D | vhost_crypto.rst | 43 * socket-file lcore,PATH: the path of UNIX socket file to be created and
60 a SW crypto device/s (virtual crypto PMD) must be created (using --vdev).
|
| H A D | kernel_nic_interface.rst | 145 be created for the physical port ``port`` and the KNI kernel thread(s)
149 will be created for each lcore ID specified, bound to the physical port
151 kernel thread <kni_kernel_thread_mode>` mode, a kernel thread will be created
199 ``vEth0_0`` is created for port 0 and one KNI interface ``vEth1_0`` is
200 created for port 1. Since ``rte_kni`` is loaded in "single kernel thread"
|
| H A D | l2_forward_event.rst | 154 Once the arguments are parsed, the mbuf pool is created.
290 In case of S/W scheduler, an extra event queue is created which will be used for
307 In case of S/W scheduler, an extra event port is created by DPDK library which
312 :start-after: Extra port created. 8<
313 :end-before: >8 End of extra port created.
|
| H A D | ipv4_multicast.rst | 112 The hash object is created and loaded with the pre-configured entries read from a global array:
116 :start-after: Hash object is created and loaded. 8<
117 :end-before: >8 End of hash object is created and loaded.
|
| /dpdk/doc/guides/prog_guide/ |
| H A D | kernel_nic_interface.rst | 56 off Interfaces will be created with carrier state set to off.
57 on Interfaces will be created with carrier state set to on.
72 network stack. Without any parameters, only one kernel thread is created
124 in ``struct rte_kni_conf`` when the first KNI interface is created:
130 thread for each KNI interface created by the DPDK application. Multiple
140 parameters in ``struct rte_kni_conf`` when each KNI interface is created.
153 The default carrier state of KNI interfaces created by the ``rte_kni``
241 Before any KNI interfaces can be created, the ``rte_kni`` kernel module must
244 The KNI interfaces are created by a DPDK application dynamically via the
|
| H A D | overview.rst | 21 These environments are created through the use of meson files and configuration files.
22 Once the EAL library is created, the user may link with the library to create their own application…
44 Once these libraries are created for the specific environment and architecture,
123 The message buffers are created at startup time and stored in a mempool, using the DPDK mempool lib…
|
| H A D | traffic_metering_and_policing.rst | 31 The MTR objects are created and updated in their own name space (``rte_mtr``)
36 Once successfully created, an MTR object is hooked into the RX processing path
90 function. One of the previously created meter profile
|
| H A D | stack_lib.rst | 19 * Free a previously created stack.
65 fixed maximum depth, these elements do not need to be dynamically created.
|
| H A D | pcapng_lib.rst | 26 The output stream is created with ``rte_pcapng_fdopen``,
|
| /dpdk/doc/guides/nics/ |
| H A D | octeontx.rst | 93 PMD: octeontx_probe(): created ethdev eth_octeontx for port 0
94 PMD: octeontx_probe(): created ethdev eth_octeontx for port 1
113 PKI/PKO PCIe VF devices will be probed and then the vdev device can be created
|
| H A D | pcap_ring.rst | 26 to be created at application startup time during EAL initialization.
35 Pcap-based devices can be created using the virtual device --vdev option.
67 The file is overwritten if it already exists and it is created if it does not.
125 In this case, one tx drop queue is created for each rxq on that device.
133 In this case, one dummy rx queue is created for each tx queue argument passed
316 Once an ethdev has been created, for either a ring or a pcap-based PMD,
|
| H A D | cnxk.rst | 76 EAL: No legacy callbacks, legacy socket not created
283 With the above configuration, Outbound CPT LF will be created to accommodate
326 rule is created in the MCAM entry and matches it exactly. This behaviour can
335 created with RTE_FLOW_ACTION_TYPE_SECURITY action. Since channel number is
343 By default, for rules created on the SDP device, the RTE Flow API sets the
354 created on the SDP device. This option needs to be used when more than one
355 SDP interface is in use and RTE Flow rules created need to distinguish
|
| H A D | kni.rst | 44 There is no hard limit on number of interfaces that can be created.
71 With ``no_request_thread`` option, pthread is not created and control commands
|
| /dpdk/doc/guides/linux_gsg/ |
| H A D | linux_eal_parameters.rst | 90 existing hugepage files are removed and re-created
104 Hugepage files created in this mode are also not removed
|
| H A D | eal_args.include.rst | 124 No shared files created (implies no secondary process support).
163 By default, trace output will created at ``home`` directory and parameter
|
| /dpdk/doc/guides/testpmd_app_ug/ |
| H A D | testpmd_funcs.rst | 85 Flow rule #0 created
86 Flow rule #1 created
89 Flow rule #498 created
90 Flow rule #499 created
101 Flow rule #0 created
102 Flow rule #1 created
105 Flow rule #498 created
106 Flow rule #499 created
5002 Flow rule #0 created
5691 created pattern #5
[all …]
|
| /dpdk/doc/guides/dmadevs/ |
| H A D | hisilicon.rst | 31 The name of the ``dmadev`` created is like "B:D.F-chX", e.g. DMA 0000:7b:00.0
|
| /dpdk/doc/guides/cryptodevs/ |
| H A D | armv8.rst | 53 The corresponding device can be created only if the following features
|
| /dpdk/doc/guides/eventdevs/ |
| H A D | dpaa.rst | 49 probed and then vdev device can be created from the application code by
|
| H A D | dpaa2.rst | 52 probed and then vdev device can be created from the application code by
|
| /dpdk/doc/guides/rawdevs/ |
| H A D | dpaa2_cmdif.rst | 60 can be created from the application code by
|
| /dpdk/doc/api/ |
| H A D | meson.build | 11 # is in a subdirectory that is created at build time and thus it cannot
|