| /dpdk/doc/guides/sample_app_ug/ |
| H A D | multi_process.rst | 6 Multi-process Sample Application
30 Basic Multi-process Example
75 To run the secondary process to communicate with the primary process,
83 …ng the parameter altogether will cause the process to try and start as a primary rather than secon…
85 Once the process type is specified correctly,
106 The secondary process can be stopped and restarted without affecting the primary process.
132 Symmetric Multi-process Example
152 Each process reads a different RX queue on each port and so does not contend with any other process…
231 Client-Server Multi-process Example
253 The server process must be run initially as the primary process to set up all memory structures for…
[all …]
|
| H A D | server_node_efd.rst | 42 Upon initializing, the frontend server node (process) creates a flow
46 The sample application assigns a specific target node_id (process) for each of
57 The main loop of the server process receives a burst of packets, then for
70 Upon initializing, the worker node (process) creates a flow table (a regular
135 The first process, the front-end server, creates and populates the EFD table,
156 After this, a new burst of packets is received and this process is
164 The second process, the back-end node, receives the packets from the shared
167 At initialization, it attaches to the server process memory, to have
172 :start-after: Attaching to the server process memory. 8<
173 :end-before: >8 End of attaching to the server process memory.
[all …]
|
| /dpdk/doc/guides/prog_guide/ |
| H A D | pdump_lib.rst | 12 The library uses a generic multi process channel to facilitate communication
13 between primary and secondary process for enabling/disabling packet capture on
51 The primary process using ``librte_pdump`` is responsible for initializing the packet
53 multi process channel to facilitate communication with secondary process, so the
54 secondary process ``app/pdump`` tool is responsible for enabling and disabling the packet capture o…
59 …ry API ``rte_pdump_init()``, initializes the packet capture framework by creating the multi process
60 …nel using ``rte_mp_action_register()`` API. The primary process will listen to secondary process r…
61 to enable or disable the packet capture over the multi process channel.
65 the request to the primary process over the multi process channel. The primary process takes this r…
68 the rte_ring that secondary process have passed to these APIs.
[all …]
|
| H A D | multi_proc_support.rst | 6 Multi-process Support
17 For now, there are two types of process specified:
35 To support these two process types, and other multi-process setups described later,
54 On application start-up in a primary or standalone process,
63 Refer to `Multi-process Limitations`_ for details of
86 DPDK multi-process support can be used to create a set of peer processes where each process perform…
134 Any network ports being used by one process should be blocked by every other process.
149 Multi-process Limitations
156 This makes secondary process startup process generally unreliable. Disabling
175 …to transfer the interrupt information from the primary process to any secondary process that needs…
[all …]
|
| H A D | generic_receive_offload_lib.rst | 9 small packets into larger ones, GRO enables applications to process
20 types. One GRO type is in charge of process one kind of packets. For
31 6864 to process the IPv4 ID field.
50 which process N packets at a time. Using the lightweight mode API to
58 packets that ``rte_gro_reassemble_burst()`` can process in an invocation
114 fields (we call them as "key"). To process an input packet, the algorithm
189 We comply RFC 6864 to process the IPv4 ID field. Specifically,
206 - GRO library doesn't support to process the packets with IPv4
209 - GRO library just supports to process the packet organized
|
| H A D | packet_distrib_lib.rst | 32 …The process API call will poll all the worker cache lines to see what workers are requesting packe…
44 #. Once all input packets passed to the process API have either been distributed to workers
46 then the process API returns to the caller.
57 which should only be called on the lcore which also calls the process API.
71 Using the process and returned_pkts API, the following application workflow can be used,
81 are likely of less use that the process and returned_pkts APIS, and are principally provided to aid…
|
| H A D | lpm6_lib.rst | 75 or the subsequent tbl8s we might need to continue the lookup process in deeper levels of the tree.
81 By splitting the process in different tables/levels and limiting the number of tbl8s,
102 The first field can either contain a number indicating the tbl8 in which the lookup process should …
106 and whether the search process have finished or not respectively.
129 and the external entry flag to 0 (meaning the lookup process ends at this point,
140 (meaning the lookup process must continue since the rule hasn't been explored completely).
144 * Repeat the process until the tbl8 at the right level (depending on the depth) has been reached
154 By doing this we ensure that during the lookup process, if a rule matching the IP address exists,
165 The lookup process is much simpler and quicker. In this case:
176 * Repeat the process until either we find an invalid entry (lookup miss) or a valid entry with th…
|
| H A D | graph_lib.rst | 24 - Multi-process support.
70 process():
75 A graph node process the function using ``process()`` and enqueue to next
82 information. This memory will be used by process(), init(), fini() callbacks.
124 While performing the graph walk, the ``process()`` function of all the source
133 using the constructor scheme. The constructor scheme used here to support multi-process.
256 The ``process()`` function of a node is the fast-path function and that needs
265 ``process()`` function can move the obj burst to the next node either using
299 and process current pkt_set to find their next node
309 5. if n_left_from != 0 then goto 3) to process remaining packets.
|
| H A D | thread_safety_dpdk_functions.rst | 12 In some cases, it is not only multi-threaded, but multi-process.
49 For example, malloc and memzone functions are safe for use in multi-threaded and multi-process envi…
64 In the multi-process case, the configuration information of shared memory will only be initialized …
|
| /dpdk/lib/eal/windows/ |
| H A D | eal_memory.c | 276 HANDLE process; in eal_mem_reserve() local
285 process = GetCurrentProcess(); in eal_mem_reserve()
298 if (!VirtualFreeEx(process, virt, 0, MEM_RELEASE)) in eal_mem_reserve()
324 HANDLE process; in eal_mem_commit() local
330 process = GetCurrentProcess(); in eal_mem_commit()
344 process, requested_addr, size, flags)) { in eal_mem_commit()
399 HANDLE process; in eal_mem_decommit() local
403 process = GetCurrentProcess(); in eal_mem_decommit()
450 HANDLE process; in mem_free() local
452 process = GetCurrentProcess(); in mem_free()
[all …]
|
| H A D | eal_debug.c | 21 HANDLE process = GetCurrentProcess(); in rte_dump_stack() local
23 ret = SymInitialize(process, NULL, TRUE); in rte_dump_stack()
46 ret = SymFromAddr(process, address, &sym_disp, symbol_info); in rte_dump_stack()
60 ret = SymGetLineFromAddr64(process, address, &lin_disp, &line); in rte_dump_stack()
77 ret = SymCleanup(process); in rte_dump_stack()
|
| /dpdk/lib/ipsec/ |
| H A D | sa.c | 704 pf->process = esp_inb_tun_pkt_process; in lksd_none_pkt_func_select()
708 pf->process = esp_inb_trs_pkt_process; in lksd_none_pkt_func_select()
713 pf->process = (sa->sqh_len != 0) ? in lksd_none_pkt_func_select()
718 pf->process = (sa->sqh_len != 0) ? in lksd_none_pkt_func_select()
742 pf->process = esp_inb_tun_pkt_process; in cpu_crypto_pkt_func_select()
746 pf->process = esp_inb_trs_pkt_process; in cpu_crypto_pkt_func_select()
751 pf->process = (sa->sqh_len != 0) ? in cpu_crypto_pkt_func_select()
756 pf->process = (sa->sqh_len != 0) ? in cpu_crypto_pkt_func_select()
783 pf->process = inline_inb_tun_pkt_process; in inline_crypto_pkt_func_select()
825 pf->process = pkt_flag_process; in ipsec_sa_pkt_func_select()
[all …]
|
| H A D | rte_ipsec.h | 45 uint16_t (*process)(const struct rte_ipsec_session *ss, member
158 return ss->pkt_func.process(ss, mb, num); in rte_ipsec_pkt_process()
|
| /dpdk/doc/guides/tools/ |
| H A D | pdump.rst | 10 a DPDK secondary process and is capable of enabling packet capture on dpdk ports.
26 * The ``dpdk-pdump`` tool runs as a DPDK secondary process. It exits when
75 …in the primary process due to a bug in the ethdev library. Due to this bug, in a multi process con…
76 when the primary and secondary have different ports set, then the secondary process
77 …(here the ``dpdk-pdump`` tool) overwrites the ``rte_eth_devices[]`` entries of the primary process.
|
| H A D | dumpcap.rst | 10 It runs as a secondary DPDK process and lets you capture packets
11 that are coming into and out of a DPDK primary process.
35 * The ``dpdk-dumpcap`` tool runs as a DPDK secondary process.
|
| /dpdk/buildtools/ |
| H A D | call-sphinx-build.py | 32 process = run(sphinx_cmd + ['-b', 'html', src, join(dst, 'html')], variable
39 sys.exit(process.returncode)
|
| /dpdk/lib/graph/ |
| H A D | node.c | 71 if (reg == NULL || reg->process == NULL) { in __rte_node_register()
91 node->process = reg->process; in __rte_node_register()
161 reg->process = node->process; in node_clone()
|
| /dpdk/doc/guides/testpmd_app_ug/ |
| H A D | run_app.rst | 573 The following are the command-line options for testpmd multi-process support:
575 * primary process:
582 * secondary process:
597 The ID of the current process (ID < num-procs). ID should be different in
598 primary process and secondary process, which starts from '0'.
603 Calculation rule for the testpmd to allocate queues to each process:
609 queues 0 and 1 will be used by the primary process and
610 queues 2 and 3 will be used by the secondary process.
617 All the dev ops is supported in primary process. While secondary process is
630 secondary process, like:
[all …]
|
| /dpdk/doc/guides/howto/ |
| H A D | telemetry.rst | 19 socket with path */var/run/dpdk/\*/dpdk_telemetry.v2* (when the primary process
95 When multiple DPDK process instances are running on a system, the user will
102 the file-prefix for the process should be passed via the `-f` or `--file-prefix` script flag.
120 each process after the first will add an increasing count suffix to the telemetry socket name,
|
| /dpdk/devtools/ |
| H A D | process-iwyu.py | 68 def process(args): function
105 process(args_parse())
|
| /dpdk/doc/guides/contributing/ |
| H A D | vulnerability.rst | 11 are in the scope of this security process (including experimental APIs).
46 as part of the security process.
51 as that can speed up the process considerably.
60 the reporting process must be followed anyway, as described below.
70 Area experts not members of the security team may be involved in the process.
90 using the standard patch process, once a CVE number has been assigned.
166 as described below. It must not be considered as the standard process.
199 OSS-security process <https://oss-security.openwall.org/wiki/mailing-lists/distros>`
318 * `A minimal security response process
|
| /dpdk/app/test-bbdev/ |
| H A D | test-bbdev.py | 14 def kill(process): argument
16 process.kill()
|
| /dpdk/app/test-crypto-perf/ |
| H A D | dpdk-graph-crypto-perf.py | 163 process = subprocess.Popen(["stdbuf", "-oL", test_cmd] + params,
170 while process.poll() is None:
171 line = process.stdout.readline().strip()
185 if process.poll() != 0 or not columns or not rows:
|
| /dpdk/buildtools/chkincs/ |
| H A D | meson.build | 19 sources += gen_c_files.process(dpdk_chkinc_headers)
55 cpp_sources += gen_cpp_files.process(dpdk_chkinc_headers)
|
| /dpdk/app/test/ |
| H A D | test_graph.c | 86 rte_node_process_t process; member
105 .process = test_node0_worker,
116 .process = test_node1_worker,
125 .process = test_node2_worker,
134 .process = test_node3_worker,
153 .process = test_node_worker_source,
163 .process = test_node0_worker,
|