| /dpdk/doc/guides/prog_guide/ |
| H A D | thread_safety_dpdk_functions.rst | 8 Some of the functions in these libraries can be safely called from multiple threads simultaneously,…
13 Typically, it is best to avoid sharing data structures between threads and/or processes where possi…
22 certain functions within those libraries may not be safe to call from multiple threads simultaneous…
28 lookups of values can be performed in parallel in multiple threads.
30 cannot be done in multiple threads without using locking when a single hash or LPM table is accesse…
35 Note, however, that these functions can safely be used from multiple threads
37 If multiple threads are to use the same hardware queue on the same NIC port,
60 rather than subsequently in the forwarding threads.
72 callbacks may be called in an additional thread outside the main DPDK processing threads.
73 … callbacks should avoid manipulating DPDK objects that are also managed by the normal DPDK threads,
|
| H A D | rcu_lib.rst | 87 The length of the critical section and the number of reader threads
122 of memory to allocate. This API takes a maximum number of reader threads,
131 maximum number of threads provided while creating the QS variable.
140 Some of the use cases might require the reader threads to make blocking API
147 The writer thread can trigger the reader threads to report their quiescent
149 writer threads to query the quiescent state status simultaneously. Hence,
154 threads enter the quiescent state is provided. If this API indicates that
155 all the reader threads have entered the quiescent state, the application
160 running as worker threads.
163 the writer threads flexibility to do useful work instead of blocking for the
[all …]
|
| H A D | stack_lib.rst | 47 lock-free property means that multiple threads can push and pop simultaneously,
79 2. Other threads modify the list such that the head pointer is once again X,
|
| H A D | packet_framework.rst | 68 … | SW circular buffer used for message passing between the application threads. Uses |
1113 The threads performing table lookup are actually table writers rather than just readers.
1119 for data consistency reasons, no other threads (threads performing table lookup or entry add/delete…
1121 Mechanisms to share the same table between multiple threads:
1123 #. **Multiple writer threads.**
1128 #. **Multiple writer threads, with single thread performing table lookup operations and multiple t…
1129 …The threads performing table entry add/delete operations send table update requests to the reader …
1132 #. **Single writer thread performing table entry add/delete operations and multiple reader threads…
1133 The reader threads use the main table copy while the writer is updating the mirror copy.
|
| H A D | glossary.rst | 31 A core may include several lcores or threads if the processor supports
|
| /dpdk/lib/pipeline/ |
| H A D | rte_swx_pipeline.c | 192 struct thread *t = &p->threads[i]; in struct_build()
207 struct thread *t = &p->threads[i]; in struct_build_free()
812 struct thread *t = &p->threads[i]; in extern_obj_build()
847 struct thread *t = &p->threads[i]; in extern_obj_build_free()
1023 struct thread *t = &p->threads[i]; in extern_func_build()
1056 struct thread *t = &p->threads[i]; in extern_func_build_free()
1221 struct thread *t = &p->threads[i]; in header_build()
1261 struct thread *t = &p->threads[i]; in header_build_free()
1339 struct thread *t = &p->threads[i]; in metadata_build()
1358 struct thread *t = &p->threads[i]; in metadata_build_free()
[all …]
|
| /dpdk/doc/guides/sample_app_ug/ |
| H A D | dist_app.rst | 64 The distributor application consists of four types of threads: a receive
66 worker threads (``lcore_worker()``), and a transmit thread(``lcore_tx()``).
67 How these threads work together is shown in :numref:`figure_dist_app` below.
68 The ``main()`` function launches threads of these four types. Each thread
78 tag. The distributor thread communicates with the worker threads using a
83 worker threads do simple packet processing by requesting packets from
96 in the application will terminate all running threads gracefully and print
|
| H A D | kernel_nic_interface.rst | 44 ``kni`` uses two DPDK threads in user space; one thread reads from the port and
135 cores are used to pin the kernel threads in the ``rte_kni`` kernel module.
290 is the association of each port with lcores for RX, TX and kernel threads.
296 * Other lcores for pinning the kernel threads on one by one
|
| H A D | ip_pipeline.rst | 17 The pipelines are mapped to application threads, with each pipeline executed by a single thread and…
19 pipelines together and mapping the pipelines to execution threads are endless, therefore this appli…
30 …eline components: input/output ports, tables, pipelines, mapping of pipelines to execution threads.
|
| H A D | vdpa.rst | 11 this application doesn't need to launch dedicated worker threads for vhost
|
| H A D | rxtx_callbacks.rst | 60 execution threads for each lcore. This function is effectively identical to
|
| H A D | intro.rst | 63 copying packets between two threads.
|
| /dpdk/drivers/regex/cn9k/ |
| H A D | cn9k_regexdev_compiler.c | 48 uint32_t threads = 1; in ree_rule_db_compile() local
104 threads, in ree_rule_db_compile()
|
| /dpdk/app/test/ |
| H A D | test_threads.c | 13 RTE_LOG_REGISTER(threads_logtype_test, test.threads, INFO);
|
| /dpdk/doc/guides/howto/ |
| H A D | pvp_reference_benchmark.rst | 45 #. On BIOS, disable turbo-boost and hyper-threads.
53 #. Disable hyper-threads at runtime if necessary or if BIOS is not accessible:
131 With this command, isolated CPUs 2 to 5 will be used as lcores for PMD threads.
246 <topology sockets='1' cores='3' threads='1'/>
|
| H A D | debug_troubleshoot.rst | 8 stages making use of single or multiple threads. Applications can use poll mode
85 lcore threads has enough cycles for ``rte_eth_rx_burst`` on the port queue
89 threads gets enough cycles.
237 * Use ``rte_mempool_cache_create`` for user threads require access to
|
| /dpdk/examples/pipeline/examples/ |
| H A D | varbit.cli | 32 ; Pipelines-to-threads mapping.
|
| H A D | learner.cli | 32 ; Pipelines-to-threads mapping.
|
| H A D | fib.cli | 55 ; Pipelines-to-threads mapping.
|
| /dpdk/doc/guides/compressdevs/ |
| H A D | qat_comp.rst | 43 in different threads.)
|
| /dpdk/doc/guides/mempool/ |
| H A D | ring.rst | 49 scenarios (multiple threads share same set of cores) the ``ring_mt_rts`` or
|
| H A D | stack.rst | 35 stack whose threads can be preempted can suffer from brief, infrequent
|
| /dpdk/doc/guides/eventdevs/ |
| H A D | dsw.rst | 9 and the lcore threads using them.
|
| /dpdk/ |
| H A D | meson_options.txt | 38 …'Set maximum number of cores/threads supported by EAL; "default" is different per-arch, "detect" d…
|
| /dpdk/doc/guides/rel_notes/ |
| H A D | release_20_08.rst | 12 * **Added non-EAL threads registration API.**
14 Added a new API to register non-EAL threads as lcores. This can be used by
15 applications to have its threads known to DPDK without suffering from the
|