| /dpdk/doc/guides/nics/ |
| H A D | cnxk.rst | 122 With the above configuration, reta table of size 256 is populated.
133 With the above configuration, priority level was set to 10 (0-9). Max
145 With the above configuration, pre alloc size was set to 4. Max pre alloc
157 With the above configuration, each send queue's descriptor buffer count is
169 With the above configuration, higig2 will be enabled on that port and the
190 With the above configuration, custom pre_l2 header will be enabled on that
263 configuration allows the potential for a MCAM entry to match many SAs,
333 With the above configuration, RTE Flow rules API will set the channel
340 Set channel and channel mask configuration for the SDP device. This
352 With the above configuration, RTE Flow rules API will set the channel
[all …]
|
| H A D | dpaa.rst | 24 - FMAN configuration tools and library
220 configuration beyond that will be standard Rx queues. The application can
291 2.During FMC configuration, port for which policy is being configured is
308 This is an alternate to the FMC based configuration. This library provides
309 direct ioctl based interfaces for FMAN configuration as used by the FMC tool
311 of dynamic configuration.
|
| H A D | kni.rst | 47 Default interface configuration
51 feature set controlled by a configuration struct, and KNI PMD uses a fixed
52 configuration:
|
| /dpdk/doc/guides/bbdevs/ |
| H A D | fpga_5gnr_fec.rst | 57 The bbdev test application has been tested with a configuration 40 x 1GB hugepages. The
58 hugepage configuration of a server may be examined using:
109 support SR-IOV configuration right out of the box, so it will need to be patched.
150 to VMs/Containers. The configuration involves allocating the number of hardware
154 This configuration needs to be executed at least once after reboot or PCI FLR and can
183 configuration value should be set to 36:3. The schedule algorithm is based
199 An example configuration code calling the function ``rte_fpga_5gnr_fec_configure()`` is shown
277 Alternate Baseband Device configuration tool
280 On top of the embedded configuration feature supported in test-bbdev using "- -init-device"
281 option, there is also a tool available to perform that device configuration using a companion
|
| H A D | fpga_lte_fec.rst | 56 The bbdev test application has been tested with a configuration 40 x 1GB hugepages. The
57 hugepage configuration of a server may be examined using:
108 support SR-IOV configuration right out of the box, so it will need to be patched.
149 to VMs/Containers. The configuration involves allocating the number of hardware
153 This configuration needs to be executed at least once after reboot or PCI FLR and can
182 configuration value should be set to 36:3. The schedule algorithm is based
198 An example configuration code calling the function ``rte_fpga_lte_fec_configure()`` is shown
296 Alternate Baseband Device configuration tool
299 On top of the embedded configuration feature supported in test-bbdev using "- -init-device"
300 option, there is also a tool available to perform that device configuration using a companion
|
| H A D | acc100.rst | 72 The bbdev test application has been tested with a configuration 40 x 1GB hugepages. The
73 hugepage configuration of a server may be examined using:
165 to VMs/Containers. The configuration involves allocating the number of hardware
169 This configuration needs to be executed at least once after reboot or PCI FLR and can
219 Alternate Baseband Device configuration tool
222 On top of the embedded configuration feature supported in test-bbdev using "- -init-device"
223 option mentioned above, there is also a tool available to perform that device configuration
|
| /dpdk/doc/guides/prog_guide/ |
| H A D | regexdev.rst | 52 The configuration of each RegEx device includes the following operations:
65 The ``rte_regexdev_config`` structure is used to pass the configuration
111 /**< RegEx device configuration flags, See RTE_REGEXDEV_CFG_* */
123 The configuration mode is depended on the PMD capabilities.
125 Online rule configuration is done using the following API functions:
130 Offline rule configuration can be done by adding a pointer to the compiled
131 rule database in the configuration step, or by using
|
| H A D | thread_safety_dpdk_functions.rst | 51 The setup and configuration of the PMD is not performance sensitive, but is not thread safe either.
52 It is possible that the multiple read/writes during PMD setup and configuration could be corrupted …
53 …ve, the developer can choose to add their own layer to provide thread-safe setup and configuration.
54 It is expected that, in most applications, the initial configuration of the network ports would be …
64 In the multi-process case, the configuration information of shared memory will only be initialized …
|
| H A D | rte_security.rst | 138 It will provide a configuration option for anti-replay behavior i.e. to drop
211 It will provide a configuration option for anti-replay behavior i.e. to drop
539 configuration structure which is used in the operation processing of a packet flow.
590 Security session configuration
593 Security Session configuration structure is defined as ``rte_security_session_conf``
615 The configuration structure reuses the ``rte_crypto_sym_xform`` struct for crypto related
616 configuration. The ``rte_security_session_action_type`` struct is used to specify whether the
658 Currently the library defines configuration parameters for IPsec and PDCP only.
662 IPsec related configuration parameters are defined in ``rte_security_ipsec_xform``
664 PDCP related configuration parameters are defined in ``rte_security_pdcp_xform``
[all …]
|
| /dpdk/examples/qos_sched/ |
| H A D | profile.cfg | 4 ; This file enables the following hierarchical scheduler configuration for each
9 ; * 4K pipes per subport 0 (pipes 0 .. 4095) with identical configuration:
19 ; Port configuration
24 ; Subport configuration
53 ; Pipe configuration
|
| H A D | profile_ov.cfg | 4 ; Port configuration
9 ; Subport configuration
37 ; Pipe configuration
|
| /dpdk/doc/guides/linux_gsg/ |
| H A D | build_dpdk.rst | 33 * config, buildtools: Framework-related scripts and configuration
60 later in this section. The configuration process will finish with a summary
90 DPDK has a number of options that can be adjusted as part of the build configuration process.
103 The "platform" option specifies a set a configuration parameters that will be used.
106 * ``-Dplatform=native`` will tailor the configuration to the build machine.
108 * ``-Dplatform=generic`` will use configuration that works on all machines
111 * ``-Dplatform=<SoC>`` will use configuration optimized for a particular SoC.
149 and add all which can be built to the list of tasks in the ninja build configuration file.
|
| /dpdk/doc/guides/dmadevs/ |
| H A D | idxd.rst | 42 …ccel-config <https://github.com/intel/idxd-config>`_ utility library can be used for configuration.
45 The device configuration can also be done by directly interacting with the sysfs nodes.
49 There are some mandatory configuration steps before being able to use a device with an application.
52 need to be assigned to groups, and the various other configuration options,
61 Some configuration options include:
69 Example configuration for a work queue::
80 Check the device configuration::
167 IDXD configuration requirements:
|
| /dpdk/doc/guides/sample_app_ug/ |
| H A D | vmdq_forwarding.rst | 72 The EAL, driver and PCI configuration is performed largely as in the L2 Forwarding sample applicati…
75 Where this example application differs is in the configuration of the NIC port for RX.
80 a default structure is provided for VMDq configuration to be filled in later by the application.
85 :end-before: >8 End of Empty vdmq configuration structure.
106 :start-after: Building correct configuration for vdmq. 8<
|
| H A D | qos_scheduler.rst | 22 with two or three threads per each packet flow configuration being used.
64 * --pfc "RX PORT, TX PORT, RX LCORE, WT LCORE, TX CORE": Packet flow configuration.
116 * --cfg FILE: Profile configuration to load
121 The profile configuration file defines all the port/subport/pipe/traffic class/queue parameters
122 needed for the QoS scheduler configuration.
179 The following is an example command with a single packet flow configuration:
185 This example uses a single packet flow configuration which creates one RX thread on lcore 5 reading
|
| H A D | vmdq_dcb_forwarding.rst | 88 The EAL, driver and PCI configuration is performed largely as in the L2 Forwarding sample applicati…
91 Where this example application differs is in the configuration of the NIC port for RX.
96 a default structure is provided for VMDQ and DCB configuration to be filled in later by the applica…
100 :start-after: Empty vmdq+dcb configuration structure. Filled in programmatically. 8<
101 :end-before: >8 End of empty vmdq+dcb configuration structure.
|
| H A D | dma.rst | 77 both operations are done sequentially. For each configuration an additional
79 responsible for configuration, statistics printing and safe shutdown of
214 ``rte_dma_vchan_conf`` structs. After configuration the device is started
221 :end-before: >8 End of configuration of device.
254 :end-before: >8 End of configuration of ports and number of assigned lcores.
258 corresponding to ports and lcores configuration provided by the user.
|
| H A D | l2_forward_cat.rst | 86 PQOS: Requested CAT configuration is not valid!
128 To reset or list CAT configuration and control CDP please use ``pqos`` tool
140 to reset CAT configuration:
200 CAT configuration is validated. A check is then performed (on per socket basis)
|
| /dpdk/ |
| H A D | meson.build | 32 # set up some global vars for compiler, platform, configuration, etc.
64 # do configuration and get tool paths
99 configuration: dpdk_conf,
|
| /dpdk/doc/guides/rel_notes/ |
| H A D | release_22_07.rst | 66 * Added quanta size configuration support.
74 * Added support for promisc configuration in DCF mode.
75 * Added support for MAC configuration in DCF mode.
76 * Added support for VLAN filter and offload configuration in DCF mode.
|
| /dpdk/doc/guides/rawdevs/ |
| H A D | ioat.rst | 61 …ccel-config <https://github.com/intel/idxd-config>`_ utility library can be used for configuration.
64 The device configuration can also be done by directly interacting with the sysfs nodes.
68 There are some mandatory configuration steps before being able to use a device with an application.
71 need to be assigned to groups, and the various other configuration options,
81 Some configuration options include:
89 Example configuration for a work queue::
100 Check the device configuration::
190 the configuration structure also.
|
| /dpdk/doc/guides/howto/ |
| H A D | openwrt.rst | 27 OpenWrt configuration
33 * Select ``Use glibc`` in ``Advanced configuration options (for developers)``
36 Kernel configuration
|
| /dpdk/doc/guides/eventdevs/ |
| H A D | dlb2.rst | 56 queue's scheduling types are controlled by the event queue configuration.
70 The ``nb_atomic_order_sequences`` queue configuration field sets the ordered
78 in use, no new group will be created and queue configuration will fail. (Note
80 sequence number configuration.)
111 ``RTE_EVENT_QUEUE_CFG_SINGLE_LINK`` queue configuration flag controls
267 by first stopping the device, calling the configuration function(s), then
273 Specifically, the PMD supports the following configuration sequence:
285 configuration (including port->queue links) at this time.
287 The PMD does not support the following configuration sequences:
308 scheduled. The likelihood of this case depends on the eventdev configuration,
|
| /dpdk/devtools/ |
| H A D | get-maintainer.sh | 21 Also refer to devtools/load-devel-config to store your configuration.
|
| /dpdk/doc/guides/mempool/ |
| H A D | cnxk.rst | 56 With the above configuration, the driver will set up only 512 mempools for
61 Since this configuration is per application, the end user needs to
|