| /dpdk/doc/guides/howto/ |
| H A D | packet_capture_framework.rst | 17 There are two sample applications: ``dpdk-dumpcap`` and older ``dpdk-pdump``. 35 The ``dpdk-dumpcap`` tool is designed to take 41 The ``dpdk-testpmd`` application can be used to initialize 43 and the ``dpdk-dumpcap`` tool acts as a client. 44 To view Rx or Tx packets of ``dpdk-testpmd``, 46 and then the ``dpdk-dumpcap`` tool. 47 Packets from ``dpdk-testpmd`` will be sent to the tool, 61 * The ``dpdk-pdump`` tool is an older tool 63 The ``dpdk-pdump`` tool provides more limited functionality 66 users should use ``dpdk-dumpcap`` instead. [all …]
|
| H A D | lm_virtio_vhost_user.rst | 65 cd /root/dpdk/usertools 72 cd /root/dpdk/usertools 146 cd /root/dpdk/usertools 414 /root/dpdk/usertools/dpdk-hugepages.py --show 415 /root/dpdk/usertools/dpdk-hugepages.py --setup 2G 416 /root/dpdk/usertools/dpdk-hugepages.py --show 419 /root/dpdk/usertools/dpdk-devbind.py --status 426 /root/dpdk/usertools/dpdk-devbind.py -b igb_uio 0000:00:03.0 427 /root/dpdk/usertools/dpdk-devbind.py -b igb_uio 0000:00:04.0 429 /root/dpdk/usertools/dpdk-devbind.py --status [all …]
|
| H A D | telemetry.rst | 19 socket with path */var/run/dpdk/\*/dpdk_telemetry.v2* (when the primary process 45 ./app/dpdk-testpmd 49 ./usertools/dpdk-telemetry.py 53 Connecting to /var/run/dpdk/rte/dpdk_telemetry.v2 106 $ ./build/app/dpdk-testpmd -l 2,3 --file-prefix="tpmd" 110 $ ./usertools/dpdk-telemetry -f "tpmd" 114 $ ./usertools/dpdk-telemetry -l 126 $ ./build/app/dpdk-testpmd -l 2,3 --in-memory # will use socket "dpdk_telemetry.v2" 128 $ ./build/app/test/dpdk-test -l 4,5 --in-memory # will use "dpdk_telemetry.v2:1" 132 $ ./usertools/dpdk-telemetry.py # will connect to testpmd [all …]
|
| H A D | lm_bond_virtio_sriov.rst | 59 cd /root/dpdk/host_scripts 79 cd /root/dpdk/host_scripts 91 cd /root/dpdk/vm_scripts 584 /root/dpdk/usertools/dpdk-hugepages.py --show 585 /root/dpdk/usertools/dpdk-hugepages.py --setup 2G 586 /root/dpdk/usertools/dpdk-hugepages.py --show 589 /root/dpdk/usertools/dpdk-devbind.py --status 596 /root/dpdk/usertools/dpdk-devbind.py -b igb_uio 0000:00:03.0 597 /root/dpdk/usertools/dpdk-devbind.py -b igb_uio 0000:00:04.0 599 /root/dpdk/usertools/dpdk-devbind.py --status [all …]
|
| /dpdk/doc/guides/tools/ |
| H A D | dumpcap.rst | 4 dpdk-dumpcap Application 7 The ``dpdk-dumpcap`` tool is a Data Plane Development Kit (DPDK) 12 The ``dpdk-dumpcap`` writes files in Pcapng packet format. 19 If the ``-w`` option is not specified, ``dpdk-dumpcap`` writes 28 In DPDK, only the ``dpdk-testpmd`` is modified to initialize 30 So, if the ``dpdk-dumpcap`` tool has to be used with any application 31 other than the ``dpdk-testpmd``, user needs to explicitly modify 35 * The ``dpdk-dumpcap`` tool runs as a DPDK secondary process. 54 # <build_dir>/app/dpdk-dumpcap --list-interfaces 62 # <build_dir>/app/dpdk-dumpcap -f 'tcp port 80' [all …]
|
| H A D | devbind.rst | 4 dpdk-devbind Application 7 The ``dpdk-devbind`` tool is a Data Plane Development Kit (DPDK) utility 19 dpdk-devbind [options] DEVICE1 DEVICE2 .... 72 While any user can run the ``dpdk-devbind.py`` script to view the status of the network ports, 81 dpdk-devbind --status 85 dpdk-devbind --bind=vfio-pci eth1 89 dpdk-devbind -u 0000:01:00.0 93 dpdk-devbind -b ixgbe 02:00.0 02:00.1 98 dpdk-devbind --status 109 sudo dpdk-devbind -b vfio-pci 0000:0a:00.0 [all …]
|
| H A D | pdump.rst | 6 dpdk-pdump Application 9 The ``dpdk-pdump`` tool is a Data Plane Development Kit (DPDK) tool that runs as 10 a DPDK secondary process and is capable of enabling packet capture on dpdk ports. 13 * The ``dpdk-pdump`` tool can only be used in conjunction with a primary 15 In dpdk, only the ``testpmd`` is modified to initialize packet capture 16 framework, other applications remain untouched. So, if the ``dpdk-pdump`` 22 * The ``dpdk-pdump`` tool depends on DPDK pcap PMD, so the system should 26 * The ``dpdk-pdump`` tool runs as a DPDK secondary process. It exits when 37 ./<build_dir>/app/dpdk-pdump -- 74 * As of now the ``dpdk-pdump`` tool cannot capture the packets of virtual devices [all …]
|
| H A D | hugepages.rst | 4 dpdk-hugepages Application 7 The ``dpdk-hugepages`` tool is a Data Plane Development Kit (DPDK) utility 19 dpdk-hugepages [options] 65 While any user can run the ``dpdk-hugepages.py`` script to view the 74 dpdk-hugepages.py -s 78 dpdk-hugepages.py -p 1G --setup 2G
|
| H A D | pmdinfo.rst | 5 dpdk-pmdinfo Application 8 The ``dpdk-pmdinfo`` tool is a Data Plane Development Kit (DPDK) utility that 19 dpdk-pmdinfo [-hrtp] [-d <pci id file] <elf-file> 25 -p, --plugindir Scan dpdk for autoload plugins
|
| H A D | proc_info.rst | 4 dpdk-procinfo Application 7 The dpdk-procinfo application is a Data Plane Development Kit (DPDK) application 20 ./<build_dir>/app/dpdk-procinfo -- -m | [-p PORTMASK] [--stats | --xstats | 75 * dpdk-procinfo should run alongside primary process with same DPDK version. 77 * When running ``dpdk-procinfo`` with shared library mode, it is required to 82 * Stats retrieval using ``dpdk-procinfo`` is not supported for virtual devices like PCAP and TAP. 84 * Since default DPDK EAL arguments for ``dpdk-procinfo`` are ``-c1, -n4 & --proc-type=secondary``,
|
| /dpdk/ |
| H A D | MAINTAINERS | 28 T: git://dpdk.org/dpdk 33 T: git://dpdk.org/next/dpdk-next-net 37 T: git://dpdk.org/next/dpdk-next-net-brcm 41 T: git://dpdk.org/next/dpdk-next-net-intel 45 T: git://dpdk.org/next/dpdk-next-net-mrvl 49 T: git://dpdk.org/next/dpdk-next-net-mlx 54 T: git://dpdk.org/next/dpdk-next-virtio 58 T: git://dpdk.org/next/dpdk-next-crypto 69 T: git://dpdk.org/dpdk-stable 154 T: git://dpdk.org/dpdk [all …]
|
| /dpdk/usertools/ |
| H A D | meson.build | 5 'dpdk-devbind.py', 6 'dpdk-pmdinfo.py', 7 'dpdk-telemetry.py', 8 'dpdk-hugepages.py',
|
| /dpdk/doc/guides/windows_gsg/ |
| H A D | run_apps.rst | 34 Refer to `Windows documentation <https://git.dpdk.org/dpdk-kmods/tree/windows>`_ 35 in ``dpdk-kmods`` repository for common instructions on system setup, 70 Refer to `NetUIO documentation <https://git.dpdk.org/dpdk-kmods/tree/windows/netuio/README.rst>`_ 71 in ``dpdk-kmods`` repository for instructions to build and set up the driver. 79 Navigate to the examples in the build directory and run `dpdk-helloworld.exe`. 83 cd C:\Users\me\dpdk\build\examples 84 dpdk-helloworld.exe -l 0-3
|
| /dpdk/doc/guides/compressdevs/ |
| H A D | octeontx.rst | 70 ./usertools/dpdk-devbind.py -b vfio-pci 0001:04:00.1 71 ./usertools/dpdk-devbind.py -b vfio-pci 0001:04:00.2 72 ./usertools/dpdk-devbind.py -b vfio-pci 0001:04:00.3 73 ./usertools/dpdk-devbind.py -b vfio-pci 0001:04:00.4 74 ./usertools/dpdk-devbind.py -b vfio-pci 0001:04:00.5 75 ./usertools/dpdk-devbind.py -b vfio-pci 0001:04:00.6 76 ./usertools/dpdk-devbind.py -b vfio-pci 0001:04:00.7 77 ./usertools/dpdk-devbind.py -b vfio-pci 0001:04:01.0
|
| /dpdk/devtools/ |
| H A D | load-devel-config | 7 test ! -r /etc/dpdk/devel.config || 8 . /etc/dpdk/devel.config 10 test ! -r ~/.config/dpdk/devel.config || 11 . ~/.config/dpdk/devel.config
|
| /dpdk/.github/workflows/ |
| H A D | build.yml | 186 docker run -d -i --rm --name dpdk \ 191 run: docker exec -i dpdk dnf update -y 201 docker commit dpdk dpdk-local 206 run: docker kill dpdk 269 docker run -d -i --rm --name dpdk \ 273 -w /root/dpdk \ 274 dpdk-local 277 run: docker exec -i dpdk dnf update -y || true 284 run: docker exec -i dpdk .ci/linux-setup.sh 286 run: docker exec -i dpdk .ci/linux-build.sh [all …]
|
| /dpdk/doc/guides/cryptodevs/ |
| H A D | octeontx.rst | 90 by using dpdk-devbind.py script. The OCTEON TX crypto PF device need to be 95 Once the required VFs are enabled, dpdk-devbind.py script can be used to 101 cd <dpdk directory> 102 ./usertools/dpdk-devbind.py -u <vf device no> 103 ./usertools/dpdk-devbind.py -b vfio-pci <vf device no> 110 dpdk-hugepages.py --setup 4G --pagesize 512M 128 ./dpdk-test 136 ./dpdk-test
|
| H A D | cnxk.rst | 118 cd <dpdk directory> 119 ./usertools/dpdk-devbind.py -u 0002:10:00.1 120 ./usertools/dpdk-devbind.py -b vfio-pci 0002:10.00.1 130 dpdk-hugepages.py --setup 4G --pagesize 512M 158 cd <dpdk directory> 159 ./usertools/dpdk-devbind.py -u 0002:20:00.1 160 ./usertools/dpdk-devbind.py -b vfio-pci 0002:20:00.1 200 ./dpdk-test 207 ./dpdk-test 217 ./dpdk-test [all …]
|
| /dpdk/doc/guides/contributing/ |
| H A D | stable.rst | 59 https://git.dpdk.org/dpdk-stable where bugfixes will be backported to. 73 the latest `stable roadmap <https://core.dpdk.org/roadmap/#stable>`_. 87 Fixes suitable for backport should have a ``Cc: stable@dpdk.org`` tag in the 95 Cc: stable@dpdk.org 100 Fixes not suitable for backport should not include the ``Cc: stable@dpdk.org`` tag. 132 The Stable and LTS release are coordinated on the stable@dpdk.org mailing 136 should also be CCed to the `stable@dpdk.org <https://mails.dpdk.org/listinfo/stable>`_ 146 * Uploading a tarball of the release to dpdk.org. 147 * Sending an announcement to the `announce@dpdk.org <https://mails.dpdk.org/listinfo/announce>`_ 150 Stable releases are available on the `dpdk.org download page <https://core.dpdk.org/download/>`_.
|
| H A D | unit_test.rst | 21 The primary tools are the `dpdk-test` application, 27 with respect to `dpdk-test` and ``meson test``. 48 $ ./build/app/test/dpdk-test --dpdk-options-here 68 before invoking the `dpdk-test` command, such as:: 70 $ DPDK_TEST=version_autotest ./build/app/test/dpdk-test --dpdk-options-here 94 $ ./build/app/test/dpdk-test --dpdk-options-here version_autotest version_autotest 146 [2543/2543] Linking target app/test/dpdk-test. 160 [2543/2543] Linking target app/test/dpdk-test. 170 Adding tests to dpdk-test application 364 [2543/2543] Linking target app/test/dpdk-test. [all …]
|
| H A D | vulnerability.rst | 10 Only the main repositories (dpdk and dpdk-stable) of the core project 39 to `security@dpdk.org <https://core.dpdk.org/security#contact>`_. 43 <https://mails.dpdk.org/roster/security>`_. 76 <https://bugs.dpdk.org/buglist.cgi?f1=bug_group&o1=equals&v1=security>`_) 183 (`security-prerelease@dpdk.org <mailto:security-prerelease@dpdk.org>`_), 191 <https://mails.dpdk.org/roster/security-prerelease>`_), are: 195 have made the request to `techboard@dpdk.org <mailto:techboard@dpdk.org>`_ 243 (`security-prerelease@dpdk.org <mailto:security-prerelease@dpdk.org>`_), 287 to `announce@dpdk.org <mailto:announce@dpdk.org>`_ and to `the public OSS-security 291 Patches are then sent to `dev@dpdk.org <mailto:dev@dpdk.org>`_ [all …]
|
| H A D | patches.rst | 31 The mailing list for DPDK development is `dev@dpdk.org <https://mails.dpdk.org/archives/dev/>`_. 81 T: git://dpdk.org/next/dpdk-next-crypto 136 git clone git://dpdk.org/dpdk 137 git clone https://dpdk.org/git/dpdk 141 git clone git://dpdk.org/next/dpdk-next-* 142 git clone https://dpdk.org/git/next/dpdk-next-* 328 should also be CCed to the `stable@dpdk.org <https://mails.dpdk.org/listinfo/stable>`_ 337 Cc: stable@dpdk.org 449 ~/.config/dpdk/devel.config 450 /etc/dpdk/devel.config. [all …]
|
| /dpdk/.ci/ |
| H A D | linux-build.sh | 43 sudo sysctl -w kernel.core_pattern=/tmp/dpdk-core.%e.%p 47 ls /tmp/dpdk-core.*.* 2>/dev/null || return 0 48 for core in /tmp/dpdk-core.*.*; do 140 REF_GIT_REPO=${REF_GIT_REPO:-https://dpdk.org/git/dpdk} 147 refsrcdir=$(readlink -f $(pwd)/../dpdk-$REF_GIT_TAG)
|
| /dpdk/doc/guides/sample_app_ug/ |
| H A D | compiling.rst | 16 cd dpdk/<build_dir> 33 Applications are output to: ``dpdk/<build_dir>/examples``. 47 cd dpdk/<build_dir> 69 applications are located in ``dpdk/examples/``.
|
| /dpdk/app/test/ |
| H A D | test_trace_register.c | 9 RTE_TRACE_POINT_REGISTER(app_dpdk_test_tp, app.dpdk.test.tp) 10 RTE_TRACE_POINT_REGISTER(app_dpdk_test_fp, app.dpdk.test.fp)
|