Home
last modified time | relevance | path

Searched refs:run (Results 1 – 25 of 191) sorted by relevance

12345678

/dpdk/.github/workflows/
H A Dbuild.yml9 run:
83 run: |
143 run: |
173 run: |
184 run: |
200 run: |
206 run: docker kill dpdk
235 run: |
250 run: |
261 run: |
[all …]
/dpdk/doc/guides/prog_guide/
H A Dmeson_ut.rst7 This section describes how to run test cases with the DPDK meson build system.
23 These tests can be run using the argument to ``meson test`` as
40 If desired, additional arguments can be passed to the test run via the meson
42 For example, tests will by default run on as many available cores as is needed
44 To run the fast-tests suite using only cores 8 through 16, one can use::
52 Test cases are run serially by default for better stability.
56 * ``is_parallel`` is used to run test case either in parallel or non-parallel mode.
65 their environment. If a test can't run, then it should be skipped, as described
73 or config flags, without which the test cases cannot be run. Such test cases
74 will be reported as skipped if they cannot run. To enable those test cases,
/dpdk/doc/guides/howto/
H A Dtelemetry.rst19 socket with path */var/run/dpdk/\*/dpdk_telemetry.v2* (when the primary process
20 is run by a root user).
40 The following steps show how to run an application with telemetry support,
53 Connecting to /var/run/dpdk/rte/dpdk_telemetry.v2
98 instances are run:
100 * For DPDK processes run using a non-default file-prefix,
104 For example, to connect to testpmd run as::
116 * For the case where multiple processes are run using the `--in-memory` EAL flag,
124 For example, if the following two applications are run in separate terminals::
H A Dvirtio_user_for_container_networking.rst88 docker run -i -t -v /tmp/sock0:/var/run/usvhost \
91 --vdev=virtio_user0,path=/var/run/usvhost \
95 Note: If we run all above setup on the host, it's a shm-based IPC.
H A Dlm_virtio_vhost_user.rst78 For Fortville and Niantic NIC's reset SRIOV and run the
112 Setup DPDK in the VM and run testpmd in the VM.
159 For Fortville and Niantic NIC's reset SRIOV, and run
263 # This script is run on the host 10.237.212.46 to reset SRIOV
328 # This script is run on both hosts when the VM is up,
339 # This script is run on the host 10.237.212.131 to reset SRIOV
/dpdk/buildtools/
H A Dgen-pmdinfo-cfile.py13 for name in subprocess.run([ar, "t", archive], stdout=subprocess.PIPE,
18 subprocess.run([ar, "x", os.path.abspath(archive), name],
21 subprocess.run(pmdinfogen + paths + [output], check=True)
H A Dcall-sphinx-build.py9 from subprocess import run, PIPE, STDOUT
19 ver = run([sphinx, '--version'], stdout=PIPE,
32 process = run(sphinx_cmd + ['-b', 'html', src, join(dst, 'html')],
H A Dbinutils-avx512-check.py16 subprocess.run(cc + ['-c', '-xc', '-o', obj.name, '-'], input=src, check=True)
17 asm = subprocess.run([objdump, '-d', '--no-show-raw-insn', obj.name],
/dpdk/drivers/net/memif/
H A Drte_eth_memif.c211 (1 << pmd->run.log2_ring_size); in memif_get_ring()
427 d0->length = pmd->run.pkt_buffer_size; in eth_memif_rx()
627 pmd->run.pkt_buffer_size : d0->length; in eth_memif_tx()
949 r->pkt_buffer_offset = (pmd->run.num_c2s_rings + pmd->run.num_s2c_rings) * in memif_region_init_shm()
951 (1 << pmd->run.log2_ring_size)); in memif_region_init_shm()
957 (1 << pmd->run.log2_ring_size) * in memif_region_init_shm()
958 (pmd->run.num_c2s_rings + in memif_region_init_shm()
959 pmd->run.num_s2c_rings)); in memif_region_init_shm()
1075 slot = (i + pmd->run.num_c2s_rings) * in memif_init_rings()
1448 pmd->run.num_s2c_rings; in memif_stats_get()
[all …]
H A Dmemif_socket.c172 pmd->run.num_c2s_rings = RTE_MIN(h->max_c2s_ring + 1, in memif_msg_receive_hello()
174 pmd->run.num_s2c_rings = RTE_MIN(h->max_s2c_ring + 1, in memif_msg_receive_hello()
176 pmd->run.log2_ring_size = RTE_MIN(h->max_log2_ring_size, in memif_msg_receive_hello()
178 pmd->run.pkt_buffer_size = pmd->cfg.pkt_buffer_size; in memif_msg_receive_hello()
312 pmd->run.num_c2s_rings++; in memif_msg_receive_add_ring()
318 pmd->run.num_s2c_rings++; in memif_msg_receive_add_ring()
626 memset(&pmd->run, 0, sizeof(pmd->run)); in memif_disconnect()
710 for (i = 0; i < pmd->run.num_c2s_rings; i++) { in memif_msg_receive()
716 for (i = 0; i < pmd->run.num_s2c_rings; i++) { in memif_msg_receive()
/dpdk/doc/guides/sample_app_ug/
H A Dmulti_process.rst27 the final make command can be run just in that application's directory,
39 To run the application, start one copy of the simple_mp binary in one terminal,
46 For the first DPDK process run, the proc-type flag can be omitted or set to auto,
75 To run the secondary process to communicate with the primary process,
76 again run the same binary setting at least two cores in the coremask/corelist:
174 For example, to run a set of four symmetric_mp instances, running on lcores 1-4,
176 the following commands can be used (assuming run as root):
188 …When using auto, the first process run creates all the memory structures needed for all processes -
282 as there is no support in the server application for it to run as a secondary process.
293 In the same way that the server process is designed to be run as a primary process instance only,
[all …]
H A Dpipeline.rst34 * Argument: Path to the CLI script file to be run at application startup.
35 No CLI script file will run at startup if this argument is not present.
57 The following is an example command to run the application configured for the VXLAN encapsulation e…
69 EAL: Multi-process socket /var/run/.rte_unix
75 To run remote client (e.g. telnet) to communicate with the application:
H A Dkeep_alive.rst35 such, the initialization and run-time paths are very similar to those
66 To run the application in linux environment with 4 lcores, 16 ports
83 overview section, the initialization and run-time paths are very
109 is configured to run every check_period milliseconds.
117 The rest of the initialization and run-time path follows
H A Dservice_cores.rst14 run on different service lcores. This orchestration is done by calling the
30 To run the example, just execute the binary. Since the application dynamically
71 These are the functions to start a service core, and have it run a service:
95 method of registering functions to be run, allowing the running of the
H A Dserver_node_efd.rst91 The application has two binaries to be run: the front-end server
113 First, the server app must be launched, with the number of nodes that will be run.
114 Once it has been started, the node instances can be run, with different NODE_ID.
115 These instances have to be run as secondary processes, with ``--proc-type=secondary``
119 To successfully run the application, the command line used to start the
124 refer to the DPDK Test Report. For more details on how to set up and run the
H A Dfips_validation.rst62 The application can be run with a ``.rsp`` file and what the outcome of that
64 the same as the ``.rsp`` used to run the application, this is useful for
120 To run the application in linux environment to test one AES FIPS test data
129 To run the application in linux environment to test all AES-GCM FIPS test
/dpdk/doc/guides/testpmd_app_ug/
H A Dintro.rst13 The guide shows how to build and run the testpmd application and
14 how to configure the application from the command line and the run-time environment.
/dpdk/doc/guides/windows_gsg/
H A Dintro.rst9 and run a DPDK application in a Windows* OS application environment, without
19 of any individual patch series. The goal is to be able to run any DPDK
/dpdk/doc/guides/freebsd_gsg/
H A Dbuild_sample_apps.rst9 The chapter describes how to compile and run applications in a DPDK
65 A hexadecimal bit mask of the cores to run on. Note that core numbering
106 to run these applications as a user other than "root". To do so, the ownership,
108 that the user account being used to run the DPDK application has access
H A Dinstall_from_ports.rst64 These examples can be compiled and run as described in :ref:`compiling_sample_apps`.
79 compiled and run as below, where we have 2 memory blocks of size 1G reserved
94 EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
118 To run a DPDK process as a non-root user, adjust the permissions on
/dpdk/doc/guides/tools/
H A Dcomp_perf.rst9 compress tree. User can use multiple cores to run tests on but only
48 Set the hexadecimal bitmask of the cores to run on. The corelist is a
53 One lcore is needed for process admin, tests are run on all other cores.
54 To run tests on two lcores, three lcores must be passed to the tool.
H A Dtesteventdev.rst32 Set the hexadecimal bitmask of the cores to run on. The corelist is a
278 Example command to run order queue test:
341 Example command to run order ``all types queue`` test:
445 Example command to run perf queue test:
460 Example command to run perf queue test with ethernet ports:
467 Example command to run perf queue test with event timer adapter:
555 Example command to run perf ``all types queue`` test:
679 Example command to run pipeline queue test:
686 Example command to run pipeline atq test with vector events:
783 Example command to run pipeline atq test:
[all …]
/dpdk/doc/guides/contributing/
H A Dunit_test.rst11 where tests are grouped into test suites, and suites are run by runners.
39 DPDK tests are run via the main test runner, the `dpdk-test` app.
52 EAL: Multi-process socket /run/user/26934/dpdk/rte/mp_socket
61 At the prompt, simply type the name of the test suite you wish to run
74 EAL: Multi-process socket /run/user/26934/dpdk/rte/mp_socket
99 EAL: Multi-process socket /run/user/26934/dpdk/rte/mp_socket
133 These test suites can take longer to run and do performance evaluations.
165 for the ``meson test`` command to run them.
206 in this case the test cases will be run,
398 Once added, the new test will be run
[all …]
/dpdk/doc/guides/linux_gsg/
H A Dbuild_sample_apps.rst7 The chapter describes how to compile and run applications in a DPDK environment.
43 An hexadecimal bit mask of the cores to run on. Note that core numbering can
113 Copy the DPDK application binary to your target, then run the application as follows
143 On Fedora, this may be installed and run using the following commands::
161 if no ``-m`` or ``--socket-mem`` parameter is passed to it when run.
187 These sample applications may be built and run in a manner similar to that described in earlier sec…
/dpdk/doc/guides/nics/
H A Dbuild_and_test.rst9 This section demonstrates how to compile and run a Poll Mode Driver (PMD) for
17 information on how to build and run testpmd.
48 This section demonstrates how to setup and run ``testpmd`` in Linux.

12345678