└───liblfds710 ├───inc │ └───liblfds710 │ lfds710_ringbuffer.h └───src └───lfds710_ringbuffer lfds710_ringbuffer_init.c
void lfds710_ringbuffer_init_valid_on_current_logical_core( struct lfds710_ringbuffer_state *rs, struct lfds710_ringbuffer_element *re_array, lfds710_pal_uint_t number_elements, void *user_state );
struct lfds710_ringbuffer_state *rs
- A pointer to a user-allocated struct lfds710_ringbuffer_state.
struct lfds710_ringbuffer_element *re_array
- A user-allocated array of LFDS710_PAL_ATOMIC_ISOLATION_IN_BYTES aligned struct lfds710_ringbuffer_element which are the store used by the ringbuffer. The number of elements in this array must be one more than the number of elements you wish to have in the ringbuffer, as the ringbuffer uses a dummy element. Stack declared variables will automatically be correctly aligned by the compiler, due to the information in the structure definitions; nothing has to be done. Heap allocated variables however will by no means be correctly aligned and an aligned malloc must be used.
- The number of elements in the array pointed to by re_array. This is the actual real number of includes, i.e. including the dummy element.
- A pointer to void, supplied by the user, which is returned to the user in various callback functions, permitting the user to pass his own state into those functions. This argument can be NULL.
As the function name indicates, the initialization work performed on the ringbuffer state is only valid on the current logical core. To make this work valid on other logical cores, threads on other cores must call LFDS710_MISC_MAKE_VALID_ON_CURRENT_LOGICAL_CORE_INITS_COMPLETED_BEFORE_NOW_ON_ANY_OTHER_LOGICAL_CORE.
This function instantiates a ringbuffer by initializing the ringbuffer state. The caller is responsible for all memory allocation and, after lfds710_ringbuffer_cleanup is called, for all deallocation.