Home
last modified time | relevance | path

Searched refs:configured (Results 1 – 25 of 162) sorted by relevance

1234567

/dpdk/drivers/net/mvpp2/
H A Dmrvl_tm.c149 if (!priv->configured) in mrvl_node_type_get()
185 if (!priv->configured) in mrvl_capabilities_get()
241 if (!priv->configured) in mrvl_level_capabilities_get()
312 if (!priv->configured) in mrvl_node_capabilities_get()
389 if (!priv->configured) in mrvl_shaper_profile_add()
462 if (!priv->configured) in mrvl_shaper_profile_delete()
613 if (!priv->configured) in mrvl_node_add()
703 if (!priv->configured) in mrvl_node_delete()
772 if (!priv->configured) in mrvl_node_suspend()
818 if (!priv->configured) in mrvl_node_resume()
[all …]
/dpdk/doc/guides/prog_guide/
H A Dregexdev.rst19 RegEx devices to be managed and configured and supports RegEx operations to be
73 /**< Maximum matches per scan configured on this device.
102 * be configured prebuilt rule database. Application may use
118 Each Regex device should be configured with the rule database.
138 Each RegEx device can be configured with number of queue pairs.
139 Each queue pair is configured using ``rte_regexdev_queue_pair_setup``
H A Dtraffic_metering_and_policing.rst48 packet. Statistics counters are maintained for MTR object, as configured.
61 Any rte_flow action list can be configured per color for each policy.
62 A meter object configured with a policy executes the actions per packet
H A Dfib_lib.rst35 search within FIB. The size of the next hop ID is variable and must be configured
69 This algorithm will be used if the ``RTE_FIB_DUMMY`` type is configured as the
83 This algorithm will be used if the ``RTE_FIB_DIR24_8`` type is configured as the
/dpdk/drivers/event/dlb2/pf/base/
H A Ddlb2_hw_types.h130 u8 configured; member
190 u8 configured; member
270 u8 configured; member
/dpdk/doc/guides/nics/
H A Ddpaa.rst208 This defines the number of Rx queues configured for an application, per
211 In case the application is configured to use lesser number of queues than
212 configured above, it might result in packet loss (because of distribution).
217 These queues use one private HW portal per queue configured, so they are
218 limited in the system. The first configured ethdev queues will be
291 2.During FMC configuration, port for which policy is being configured is
323 queues. Start and End margin of buffer can also be configured.
H A Dcnxk.rst115 RSS redirection table size may be configured during runtime using ``reta_size``
126 RTE Flow priority levels can be configured during runtime using
162 A port can be configured to a specific switch header type by using
183 in hexadecimal format and mask should be contiguous. Info can be configured
357 specified should match all the channels(or rings) configured on the SDP
402 For ``vlan_exdsa`` and ``exdsa``, the port has to be configured with the
/dpdk/doc/guides/rawdevs/
H A Dioat.rst52 Depending on support provided by the PMD, HW devices can either use the kernel configured driver
60 …use a Intel\ |reg| DSA device bound to the IDXD kernel driver, the device must first be configured.
80 However, the work queues also need to be configured depending on the use case.
95 Once the devices have been configured, they need to be enabled::
137 allowing each DPDK application instance to only use a subset of configured queues.
174 ``rte_ioat_rawdev_config``, in which case the size of the configured device
192 The following code shows how the device is configured in
209 Once configured, the device can then be made ready for use by calling the
/dpdk/doc/guides/dmadevs/
H A Didxd.rst41 …se an Intel\ |reg| DSA device bound to the IDXD kernel driver, the device must first be configured.
60 However, the work queues also need to be configured depending on the use case.
75 Once the devices have been configured, they need to be enabled::
84 Every Intel\ |reg| DSA instance supports multiple queues and each should be similarly configured.
143 use a subset of configured queues.
174 Once configured, the device can then be made ready for use by calling the
/dpdk/drivers/event/opdl/
H A Dopdl_evdev.h132 uint8_t configured; member
187 uint8_t configured; member
H A Dopdl_evdev_init.c361 if (port->configured) { in opdl_add_event_handlers()
541 queue->configured = 1; in initialise_queue()
796 device->queue[next_qid].configured) { in initialise_all_other_ports()
840 if (port->configured && in initialise_all_other_ports()
904 port->configured = 1; in initialise_queue_zero_ports()
H A Dopdl_evdev.c120 if (!p->configured) { in opdl_port_link()
188 if (p->configured) { in opdl_port_setup()
203 p->configured = 1; in opdl_port_setup()
218 p->configured = 0; in opdl_port_release()
/dpdk/drivers/event/dlb2/
H A Drte_pmd_dlb2.c29 if (!dlb2->configured || dlb2->run_state != DLB2_RUN_STATE_STOPPED) in rte_pmd_dlb2_set_token_pop_mode()
/dpdk/doc/guides/tools/
H A Dtesteventdev.rst193 Vector timeout nanoseconds to be configured for the Rx adapter.
365 | 1 | nb_queues | nb_producers * | Queues will be configured based on the |
492 | 1 | nb_queues | nb_producers | Queues will be configured based on the |
587 | 1 | nb_queues | (nb_producers | Queues will be configured based on the |
593 | 2 | nb_producers | >= 1 | Producers will be configured based on |
595 | | | | Each ethdev will be configured as an Rx |
627 each ethernet device is configured as a event_eth_rx_adapter that acts as a
711 | 1 | nb_queues | nb_producers + | Queues will be configured based on the |
717 | 2 | nb_producers | >= 1 | Producers will be configured based on |
719 | | | | Each ethdev will be configured as an Rx |
/dpdk/doc/guides/linux_gsg/
H A Dbuild_dpdk.rst45 DPDK can be configured, built and installed on your system using the tools
65 Once configured, to build and then install DPDK system-wide use:
91 These options can be listed by running ``meson configure`` inside a configured build folder.
161 the ``pkg-config`` tool must also be configured
176 Once the build directory has been configured,
/dpdk/doc/guides/sample_app_ug/
H A Dqos_metering.rst72 The traffic meter parameters are configured in the application source code with following default v…
76 :start-after: Traffic meter parameters are configured in the application. 8<
77 :end-before: >8 End of traffic meter parameters are configured in the application.
H A Dtest_pipeline.rst20 processes it according to the actions configured in the table entries that
97 … | The action configured for all table en…
120 … | The action configured for all table en…
143 … | The action configured for all table en…
H A Ddma.rst150 Each port is configured using ``port_init()`` function. The Ethernet
151 ports are configured with local settings using the ``rte_eth_dev_configure()``
246 The function launches Rx/Tx processing functions on configured lcores
247 using ``rte_eal_remote_launch()``. The configured ports, their number
264 The function receives packets on each configured Rx queue. Depending on the
H A Dtimer.rst79 Then, the two timers are configured:
92 :end-before: >8 End of two timers configured.
/dpdk/doc/guides/howto/
H A Dflow_bifurcation.rst31 network adapters. Filters can be configured to direct specific flows to a
58 the :ref:`flow_isolated_mode` can be configured.
/dpdk/doc/guides/eventdevs/
H A Docteontx.rst111 and they can be configured by passing limits to kernel bootargs as follows:
125 as (Rx/Timer) should be limited to the above configured value.
/dpdk/doc/guides/platform/
H A Ddpaa2.rst71 DPAA2 based resources can be configured easily with the help of ready scripts
101 DPAA2 based resources can be configured easily with the help of ready scripts
H A Ddpaa.rst65 configuration will remain in the hardware till it is re-configured. This
103 DPAA based resources can be configured easily with the help of ready scripts
/dpdk/drivers/event/cnxk/
H A Dcnxk_eventdev.h103 uint8_t configured; member
196 bool configured; member
/dpdk/doc/guides/testpmd_app_ug/
H A Drun_app.rst298 RX hairpin queue is the number of RX queues as configured using --rxq.
300 as configured using --txq.
378 feature is engaged. Affects only the queues configured
384 feature is engaged. Affects only the queues configured
458 configured flow rules only (see flow command).
484 HW may be configured with another tunnel Geneve port.
608 For example, if testpmd is configured to have 4 Tx and Rx queues,

1234567