Searched refs:reader (Results 1 – 16 of 16) sorted by relevance
| /dpdk/doc/guides/prog_guide/ |
| H A D | rcu_lib.rst | 56 after the reader stops referencing D1. In other words, reader thread RT1 has 59 Similarly, since reader thread 2 is also accessing D1, the writer has to 62 However, the writer does not need to wait for reader thread 3 to enter 64 operation happened. So, reader thread 3 will not have a reference to the 87 The length of the critical section and the number of reader threads 105 reader side to a minimum. 135 to report its quiescent state. This can be called from a reader thread. 136 A control plane thread can also call this on behalf of a reader thread. 142 wait for such reader threads to enter quiescent state. The reader thread must 179 The reader thread must call ``rte_rcu_qsbr_thread_offline()`` and [all …]
|
| H A D | writing_efficient_code.rst | 225 Lock-free reader-writer concurrency is one of the common use cases in DPDK. 227 The payload or the data that the writer wants to communicate to the reader, 232 Correspondingly, on the reader side, the guard variable should be read
|
| H A D | traffic_metering_and_policing.rst | 78 This section will introduce the reader to the critical APIs to use
|
| H A D | hash_lib.rst | 91 The library uses a reader-writer lock to provide the concurrency. 94 …the reader-writer lock will use hardware transactional memory (e.g., Intel® TSX) if supported to g… 98 …AGS_RW_CONCURRENCY_LF) is set, read/write concurrency is provided without using reader-writer lock.
|
| H A D | event_ethernet_tx_adapter.rst | 25 This section will introduce the reader to the adapter API. The
|
| H A D | eventdev.rst | 11 reader. 163 This section will introduce the reader to the eventdev API, showing how to
|
| H A D | event_ethernet_rx_adapter.rst | 25 This section will introduce the reader to the adapter API. The
|
| H A D | event_timer_adapter.rst | 87 This section will introduce the reader to the event timer adapter API, showing
|
| H A D | packet_framework.rst | 1129 …ming table entry add/delete operations send table update requests to the reader (typically through… 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.
|
| /dpdk/lib/port/ |
| H A D | rte_swx_port_fd.c | 26 struct reader { struct 44 struct reader *p; in reader_create() argument 51 p = calloc(1, sizeof(struct reader)); in reader_create() 73 struct reader *p = port; in reader_free() 89 struct reader *p = port; in reader_pkt_rx() 146 struct reader *p = port; in reader_stats_read()
|
| H A D | rte_swx_port_ring.c | 26 struct reader { struct 43 struct reader *p = NULL; in reader_create() argument 54 p = calloc(1, sizeof(struct reader)); in reader_create() 85 struct reader *p = port; in reader_pkt_rx() 134 struct reader *p = port; in reader_free() 154 struct reader *p = port; in reader_stats_read()
|
| H A D | rte_swx_port_ethdev.c | 34 struct reader { struct 51 struct reader *p; in reader_create() argument 68 p = calloc(1, sizeof(struct reader)); in reader_create() 88 struct reader *p = port; in reader_pkt_rx() 139 struct reader *p = port; in reader_free() 158 struct reader *p = port; in reader_stats_read()
|
| /dpdk/doc/guides/rel_notes/ |
| H A D | release_18_11.rst | 229 * **Added lock free reader/writer concurrency to hash library (rte_hash).** 231 Lock free reader/writer concurrency prevents the readers from getting
|
| H A D | release_19_05.rst | 40 This library helps identify the quiescent state of the reader threads so
|
| /dpdk/doc/guides/contributing/ |
| H A D | coding_style.rst | 164 …``#endif`` or ``#else`` to permit the reader to easily discern where conditionally compiled code r… 165 …ons greater than 20 lines, or where a series of nested ``#ifdef``'s may be confusing to the reader.
|
| H A D | documentation.rst | 197 * Document the obvious as well as the obscure since it won't always be obvious to the reader.
|