Lines Matching refs:API

122 of memory to allocate. This API takes a maximum number of reader threads,
125 Further, the application can initialize a QS variable using the API
134 The ``rte_rcu_qsbr_thread_register()`` API will register a reader thread
137 The reader thread must call ``rte_rcu_qsbr_thread_online()`` API to start
140 Some of the use cases might require the reader threads to make blocking API
143 call ``rte_rcu_qsbr_thread_offline()`` API, before calling blocking APIs. It
144 can call ``rte_rcu_qsbr_thread_online()`` API once the blocking API call
148 state by calling the API ``rte_rcu_qsbr_start()``. It is possible for multiple
152 The writer thread must call ``rte_rcu_qsbr_check()`` API with the token to
154 threads enter the quiescent state is provided. If this API indicates that
169 The ``rte_rcu_qsbr_synchronize()`` API combines the functionality of
171 API. This API triggers the reader threads to report their quiescent state and
172 polls till all the readers enter the quiescent state or go offline. This API
176 resource can be freed immediately after ``rte_rcu_qsbr_synchronize()`` API
181 quiescent state. The ``rte_rcu_qsbr_check()`` API will not wait for this reader
184 The reader threads should call ``rte_rcu_qsbr_quiescent()`` API to indicate that
185 they entered a quiescent state. This API checks if a writer has triggered a
206 …ter runs out of resources, the writer can call ``rte_rcu_qsbr_dq_reclaim`` API to reclaim resource…
230 * client library should provide an API to register a RCU variable that it will use. It should call …