| /dpdk/buildtools/ |
| H A D | gen-pmdinfo-cfile.py | 12 paths = [] variable 16 paths.append(name) 20 paths.append(os.path.join(temp, name)) 21 subprocess.run(pmdinfogen + paths + [output], check=True)
|
| /dpdk/usertools/ |
| H A D | dpdk-telemetry.py | 59 def print_socket_options(prefix, paths): argument 64 for s in sorted(paths):
|
| H A D | dpdk-devbind.py | 624 paths = [basename(path) for path in glob(path_join(sysfs_path, _glob))] 625 if paths: 626 return paths
|
| /dpdk/doc/guides/sample_app_ug/ |
| H A D | keep_alive.rst | 35 such, the initialization and run-time paths are very similar to those 83 overview section, the initialization and run-time paths are very 118 the same paths as the L2 forwarding application. The only
|
| H A D | ip_reassembly.rst | 15 The initialization and run- time paths are very similar to those of the :doc:`l2_forward_real_virtu… 127 As mentioned in the overview section, the initialization and run-time paths are very similar to tho…
|
| H A D | ipv4_multicast.rst | 15 The initialization and run-time paths are very similar to those of the :doc:`l2_forward_real_virtua… 90 the initialization and run-time paths are very similar to those of the :doc:`l2_forward_real_virtua…
|
| H A D | ip_frag.rst | 15 The initialization and run-time paths are very similar to those of the :doc:`l2_forward_real_virtua…
|
| H A D | fips_validation.rst | 112 are folder paths.
|
| H A D | l3_forward.rst | 16 The initialization and run-time paths are very similar to those of the 228 the initialization and run-time paths are very similar to those of the :doc:`l2_forward_real_virtua…
|
| H A D | l3_forward_power_man.rst | 19 The initialization and run-time paths are very similar to those of the :doc:`l3_forward`. 120 the initialization and run-time paths are identical to those of the L3 forwarding application.
|
| H A D | l3_forward_access_ctrl.rst | 27 The initialization and run-time paths are similar to those of the :doc:`l3_forward`.
|
| H A D | ipsec_secgw.rst | 83 every type of event device without affecting existing paths/use cases. The worker
|
| /dpdk/doc/guides/nics/ |
| H A D | virtio.rst | 438 Virtio paths Selection and Usage 441 Logically virtio-PMD has 9 paths based on the combination of virtio features 461 Virtio paths Selection 464 If packed virtqueue is not negotiated, below split virtqueue paths will be selected 478 If packed virtqueue is negotiated, below packed virtqueue paths will be selected 507 Virtio paths Rx callbacks Tx callbacks 522 Virtio paths Support Status from Release to Release 533 All virtio paths support status are shown in below table: 538 Virtio paths 16.11 ~ 18.05 18.08 ~ 18.11 19.02 ~ 19.11 20.05 ~ 557 * Qemu now supports three paths of split virtqueue: Split virtqueue mergeable path,
|
| H A D | ice.rst | 261 Vector PMD for RX and TX path are selected automatically. The paths 266 If it's supported, AVX2 paths will be chosen. If not, SSE is chosen. 268 is set to 512, AVX512 paths will be chosen. 274 normal paths are chosen. 364 in the following paths in order: /lib/firmware/updates/intel/ice/ddp
|
| /dpdk/doc/guides/linux_gsg/ |
| H A D | eal_args.include.rst | 216 Specify the maximum SIMD bitwidth size to handle. This limits which vector paths, 217 if any, are taken, as any paths taken must use a bitwidth below the max bitwidth limit.
|
| H A D | build_dpdk.rst | 80 On some linux distributions, such as Fedora or Redhat, paths in `/usr/local` are 81 not in the default paths for the loader. Therefore, on these
|
| H A D | cross_build_dpdk_for_arm64.rst | 141 An example cross file with modified names and added NUMA paths 219 The paths to GNU stdlib must be specified in a cross file.
|
| /dpdk/doc/guides/rel_notes/ |
| H A D | release_21_08.rst | 40 * Added new RX and TX paths in the AVX2 code to use HW offload 42 offload paths are chosen automatically. In parallel the support for HW 43 offload features was removed from the legacy AVX2 paths.
|
| H A D | release_21_05.rst | 86 bytes of user specified information in RX and TX paths. 113 * In AVX512 code, added the new RX and TX paths to use the HW offload 115 offload paths are chosen automatically. In parallel the support for HW 116 offload features was removed from the legacy AVX512 paths.
|
| H A D | release_19_05.rst | 139 * Added support of SSE and AVX2 instructions in Rx and Tx paths.
|
| /dpdk/ |
| H A D | meson.build | 64 # do configuration and get tool paths
|
| /dpdk/doc/guides/windows_gsg/ |
| H A D | build_dpdk.rst | 114 Depending on the distribution, paths in this file may need adjustments.
|
| /dpdk/doc/guides/freebsd_gsg/ |
| H A D | build_dpdk.rst | 64 may not be in the default search paths for `.pc` files, which means
|
| /dpdk/doc/guides/contributing/ |
| H A D | coding_style.rst | 79 …pplication directory are included using quotes, while includes from other paths are included using… 745 The use of ``likely()`` and ``unlikely()`` should only be done in performance critical paths, 977 Used to indicate any additional header file paths which should be
|
| /dpdk/doc/guides/tools/ |
| H A D | testbbdev.rst | 59 Specifies paths to the test vector files. If not specified path is set based
|