| /dpdk/doc/guides/sample_app_ug/ |
| H A D | multi_process.rst | 75 To run the secondary process to communicate with the primary process,
80 ./<build_dir>/examples/dpdk-simple_mp -l 2-3 -n 4 --proc-type=secondary
105 invalidating the secondary process's pointers.
106 The secondary process can be stopped and restarted without affecting the primary process.
113 since the secondary process cannot create objects in memory as it cannot reserve memory zones,
171 The secondary symmetric_mp instances must also have these parameters specified,
196 Instead, that process can be restarted as a secondary,
197 by explicitly setting the proc-type to secondary on the command line.
211 therefore will be accessible by the secondary process as it initializes.
282 as there is no support in the server application for it to run as a secondary process.
[all …]
|
| H A D | server_node_efd.rst | 115 These instances have to be run as secondary processes, with ``--proc-type=secondary``
|
| /dpdk/doc/guides/prog_guide/ |
| H A D | pdump_lib.rst | 13 between primary and secondary process for enabling/disabling packet capture on
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…
60 channel using ``rte_mp_action_register()`` API. The primary process will listen to secondary proces…
64 For the calls to these APIs from secondary process, the library creates the "pdump enable" request …
68 the rte_ring that secondary process have passed to these APIs.
80 For the calls to these APIs from secondary process, the library creates the "pdump disable" request…
|
| H A D | multi_proc_support.rst | 21 * secondary processes, which cannot initialize shared memory,
25 while secondary processes can only run alongside a primary process or
67 ``--single-file-segments`` switch, secondary processes must be run with the
156 This makes secondary process startup process generally unreliable. Disabling
168 It is not possible to have a primary and secondary instance, or two secondary instances,
199 purpose API to exchange short messages between primary and secondary processes.
203 * Unicast message from secondary to primary
207 all secondaries, while any IPC message sent in a secondary process will only be
208 delivered to primary process. Unicast from primary to secondary or from
209 secondary to secondary is not supported.
[all …]
|
| H A D | hash_lib.rst | 131 For any input key, there are two possible buckets (primary and secondary/alternative location)
152 If signature is not in the primary bucket, the secondary bucket is looked up, where same procedure
157 Like lookup, the primary and secondary buckets are identified. If there is an empty entry in
176 Similar to lookup, the key is searched in its primary and secondary buckets. If the key is found, t…
186 reached, the secondary bucket of this key is extended
189 …key, as before, the primary bucket is searched for a match and then the secondary bucket is looked…
206 their secondary location, which the later will increase, as table gets busier.
208 are evicted to their secondary location.
|
| H A D | thread_safety_dpdk_functions.rst | 65 Thereafter, both primary and secondary processes can allocate/release any objects of memory that fi…
|
| /dpdk/drivers/net/nfp/nfpcore/ |
| H A D | nfp_nsp_cmds.c | 19 uint16_t secondary; member
59 nspi->secondary = rte_le_to_cpu_16(ni->secondary); in __nfp_nsp_identify()
|
| H A D | nfp_nsp.h | 287 uint16_t secondary; member
|
| /dpdk/doc/guides/nics/ |
| H A D | thunderx.rst | 198 Each port consists of a primary VF and n secondary VF(s). Each VF provides 8 Tx/Rx queues to a port.
199 When a given port is configured to use more than 8 queues, it requires one (or more) secondary VF.
200 Each secondary VF adds 8 additional queues to the queue set.
203 specific flag (see sqs message in DPDK boot log - sqs indicates secondary queue set).
204 They are at the beginning of VF list (the remain ones are secondary VF's).
208 8 queues than it will request for additional queues from secondary VFs.
213 driver' list, secondary VFs are on the remaining on the remaining part of the list.
285 We will choose four secondary queue sets from the ending of the list (0001:01:01.2-0002:01:02.2).
309 Use sysfs to distinguish thunder-nic primary VFs and secondary VFs.
355 Every column that ends with 'thunder-nicvf: number' can be used as secondary VF.
[all …]
|
| H A D | mlx4.rst | 129 - For secondary process:
131 - Forked secondary process not supported.
134 primary process and remapped to the same virtual address in secondary
136 different virtual address in secondary process, unexpected error may happen.
|
| H A D | nfp.rst | 139 to use specific registers inside the chip, the number of secondary processes with PF
143 is important for allowing development and debugging through the PF using a secondary
|
| H A D | tap.rst | 158 It is possible to attach an existing TAP device in a secondary process,
162 The port attached in a secondary process will give access to the
|
| /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
76 when the primary and secondary have different ports set, then the secondary process
103 the primary application to the secondary. This is an optional parameter with default size 16384.
|
| H A D | dumpcap.rst | 10 It runs as a secondary DPDK process and lets you capture packets
35 * The ``dpdk-dumpcap`` tool runs as a DPDK secondary process.
|
| H A D | proc_info.rst | 8 that runs as a DPDK secondary process and is capable of retrieving port
84 * Since default DPDK EAL arguments for ``dpdk-procinfo`` are ``-c1, -n4 & --proc-type=secondary``,
|
| /dpdk/doc/guides/linux_gsg/ |
| H A D | eal_args.include.rst | 85 * ``--proc-type <primary|secondary|auto>``
92 primary DPDK process. This can be helpful if secondary processes cannot
124 No shared files created (implies no secondary process support).
128 Use anonymous memory instead of hugepages (implies no secondary process
|
| H A D | linux_eal_parameters.rst | 53 allows running multiple independent DPDK primary/secondary processes under
|
| H A D | sys_reqs.rst | 214 If secondary process support is not required, DPDK is able to use hugepages
218 If secondary process support is required,
|
| /dpdk/doc/guides/cryptodevs/ |
| H A D | scheduler.rst | 115 worker and the secondary worker, and distributes the enqueued crypto
118 than the designated threshold, otherwise it will be handled by the secondary
122 a software cryptodev as the secondary worker. This may help applications to
144 secondary worker. In this mode, the scheduler will enqueue the incoming
146 operations fail to be enqueued, then they will be enqueued to the secondary
|
| /dpdk/doc/guides/testpmd_app_ug/ |
| H A D | run_app.rst | 582 * secondary process:
598 primary process and secondary process, which starts from '0'.
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:
640 When secondary is running, port in primary is not permitted to be stopped.
645 level: primary and secondary has its own flow list (but one flow list in HW).
648 queue allocated for secondary process is not permitted, and same for secondary
|
| /dpdk/doc/guides/howto/ |
| H A D | debug_troubleshoot.rst | 14 * single primary and single secondary
418 Use pdump in primary to allow secondary to access port-queue pair. The
419 packets get copied over in RX|TX callback by the secondary process using
425 to copy the packets, which can be shared to the secondary debug process
443 possible errors in the secondary process where the configuration fails and
459 a standalone secondary process.
|
| H A D | packet_capture_framework.rst | 33 It runs as a DPDK secondary process and captures packets
|
| /dpdk/doc/guides/rel_notes/ |
| H A D | release_19_05.rst | 78 * Added support for Rx descriptor status and related API in a secondary
80 * Added support for Tx descriptor status API in a secondary process.
82 secondary process.
83 * Added support for Rx packet types list in a secondary process.
92 * Added support for secondary processes.
106 * Added support of DMA memory registration by secondary process.
|
| H A D | known_issues.rst | 792 Restricted vdev ethdev operations supported in secondary process
796 shared between primary and secondary process. Only those Ethernet device operations
797 which based on it are workable in secondary process.
801 device in secondary process.
|
| H A D | release_16_04.rst | 15 using secondary processes.
205 * **Added mlx5 support for operation in secondary processes.**
207 Implemented TX support in secondary processes (like mlx4).
|