| /dpdk/doc/guides/freebsd_gsg/ |
| H A D | freebsd_eal_parameters.rst | 4 EAL parameters
7 This document contains a list of all EAL parameters. These parameters can be
10 Common EAL parameters
13 The following EAL parameters are common to all platforms supported by DPDK.
17 FreeBSD-specific EAL parameters
20 There are currently no FreeBSD-specific EAL command-line parameters available.
|
| /dpdk/doc/guides/linux_gsg/ |
| H A D | linux_eal_parameters.rst | 4 EAL parameters
7 This document contains a list of all EAL parameters. These parameters can be
10 Common EAL parameters
13 The following EAL parameters are common to all platforms supported by DPDK.
17 Linux-specific EAL parameters
20 In addition to common EAL parameters, there are also Linux-specific EAL
21 parameters.
|
| /dpdk/doc/guides/sample_app_ug/ |
| H A D | intro.rst | 16 Some sample applications may have their own command-line parameters described in
17 their respective guides, however all of them also share the same EAL parameters.
18 Please refer to :doc:`EAL parameters (Linux) <../linux_gsg/linux_eal_parameters>`
19 or :doc:`EAL parameters (FreeBSD) <../freebsd_gsg/freebsd_eal_parameters>` for
|
| H A D | qos_scheduler.rst | 62 Mandatory application parameters include:
68 Optional application parameters include:
100 * --rth "A, B, C": The RX queue threshold parameters
108 * --tth "A, B, C": TX queue threshold parameters
121 The profile configuration file defines all the port/subport/pipe/traffic class/queue parameters
156 Two parameters can be configured for this prior to calling any of these commands:
240 …oS Scheduler" chapter in the *DPDK Programmer's Guide* for more information about these parameters.
|
| H A D | qos_metering.rst | 31 Please refer to RFC2697 and RFC2698 for details about the srTCM and trTCM configurable parameters
72 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 D | ethtool.rst | 9 its use to query and change Ethernet card parameters. The sample
55 * ``ringparam``: Get/set ring parameters
|
| /dpdk/doc/guides/rawdevs/ |
| H A D | ifpga.rst | 37 All configuration parameters are taken by vdev_ifpga_cfg driver. Besides
80 Run-time parameters
87 The following device parameters are supported:
|
| /dpdk/doc/guides/tools/ |
| H A D | pdump.rst | 56 * Parameters inside the parentheses represents mandatory parameters.
58 * Parameters inside the square brackets represents optional parameters.
63 The ``--pdump`` parameters
|
| H A D | pmdinfo.rst | 29 * Parameters inside the square brackets represents optional parameters.
|
| H A D | cryptoperf.rst | 8 utility that allows measuring performance parameters of PMDs available in the
12 execution. Cipher parameters, type of device, type of operation and
14 parameters. These parameters are checked using device capabilities
526 The specific test cases only allow modification of app parameters,
527 and not EAL parameters.
529 to specify EAL parameters.
|
| /dpdk/doc/guides/nics/ |
| H A D | vdev_netvsc.rst | 65 Run-time parameters
71 The following device parameters are supported:
|
| H A D | build_and_test.rst | 41 The ethdev library use above options to wrap debug code to trace invalid parameters
127 #. Start ``testpmd`` with basic parameters:
|
| H A D | ark.rst | 78 The ARK PMD supports device parameters that are used for packet
80 section describes the supported parameters. These features are
83 Arkville does not require any configuration using these parameters.
98 contains configuration parameters used internally for regression
108 contains configuration parameters used internally for regression
|
| H A D | fail_safe.rst | 44 Fail-safe command line parameters
54 additional sub-device parameters if need be. They will be passed on to the
61 options provided to the EAL instead of its own parameters.
216 The first declared sub-device in the fail-safe parameters.
|
| /dpdk/doc/guides/prog_guide/ |
| H A D | kernel_nic_interface.rst | 39 The ``rte_kni`` kernel module contains several optional parameters which
70 Loading the ``rte_kni`` kernel module without any optional parameters is
72 network stack. Without any parameters, only one kernel thread is created
123 this kernel thread by setting the ``core_id`` and ``force_bind`` parameters
140 parameters in ``struct rte_kni_conf`` when each KNI interface is created.
212 The ``min_scheduling_interval`` and ``max_scheduling_interval`` parameters
235 If the ``min_scheduling_interval`` and ``max_scheduling_interval`` parameters are
|
| H A D | meson_ut.rst | 58 * ``args`` is used to specify test specific parameters (see note below).
59 * ``env`` is used to specify test specific environment parameters.
|
| /dpdk/kernel/freebsd/ |
| H A D | BSDmakefile.meson | 5 # takes parameters from the environment
|
| H A D | meson.build | 11 # target to call make, passing in the values as env parameters.
|
| /dpdk/doc/guides/cryptodevs/ |
| H A D | ccp.rst | 92 The following parameters (all optional) can be provided in the previous two calls:
117 To enable this feature, pass an additional argument as ccp_auth_opt=1 to --vdev parameters as
|
| /dpdk/doc/guides/vdpadevs/ |
| H A D | sfc.rst | 61 The following per-device parameters can be passed via EAL PCI device
65 boolean parameters value.
|
| /dpdk/examples/pipeline/examples/ |
| H A D | varbit.cli | 5 ; Customize the LINK parameters to match your setup.
|
| H A D | learner.cli | 5 ; Customize the LINK parameters to match your setup.
|
| /dpdk/doc/guides/howto/ |
| H A D | telemetry.rst | 10 ethdev port list, and eal parameters.
84 * Get the help text for a command. This will indicate what parameters are
|
| /dpdk/doc/guides/rel_notes/ |
| H A D | release_18_05.rst | 60 spawned on an as-needed basis through configuration parameters passed to the
72 * **Added PMD-recommended Tx and Rx parameters.**
353 configuration profile represents the set of configuration parameters
355 buckets. These configuration parameters were previously part of the meter
357 parameters from the meter object data structure results in reducing its
371 * ethdev: Changes to the semantics of ``rte_eth_dev_configure()`` parameters.
373 If both the ``nb_rx_q`` and ``nb_tx_q`` parameters are zero,
376 fall-back values. Previously setting both of the parameters to zero would
379 * ethdev: Changes to the semantics of ``rte_eth_rx_queue_setup()`` parameters.
387 * ethdev: Changes to the semantics of ``rte_eth_tx_queue_setup()`` parameters.
[all …]
|
| /dpdk/app/test-pmd/ |
| H A D | meson.build | 23 'parameters.c',
|