Difference between pages "r7.1.1:Struct lfds711 queue umm state" and "r7.1.1:Struct lfds711 ringbuffer element"

From liblfds.org
(Difference between pages)
Jump to navigation Jump to search
m (1 revision imported)
 
m (1 revision imported)
 
Line 1: Line 1:
{{DISPLAYTITLE:struct lfds711_queue_umm_state}}
{{DISPLAYTITLE:struct lfds711_ringbuffer_element}}
==Source File==
==Source File==
  └───liblfds711
  └───liblfds711
     └───inc
     └───inc
         └───liblfds711
         └───liblfds711
                 lfds711_queue_umm.h
                 lfds711_ringbuffer.h


==Opaque Structure==
==Opaque Structure==
  struct lfds711_queue_umm_state;
  struct lfds711_ringbuffer_element;


==Alignment==
==Alignment==
Allocations must be ''LFDS711_PAL_ATOMIC_ISOLATION_IN_BYTES'' aligned.
No alignment requirements.


==Notes==
==Notes==
This structure represents the state of a queue.  It is published in the public header file so it can be allocated on the stack, embedded in user structures and passed to ''sizeof''.  The actual internal implementation is opaque and must not be touched.
This structure represents the state of a ringbuffer element.  It is published in the public header file so it can be allocated on the stack, embedded in user structures and passed to ''sizeof''.  The actual internal implementation is opaque and must not be touched.


==See Also==
==See Also==
* [[r7.1.1:Queue (unbounded, many producer, many consumer)|Queue (unbounded, many producer, many consumer)]]
* [[r7.1.1:Ringbuffer|Ringbuffer]]
* ''[[r7.1.1:function lfds711_queue_umm_init_valid_on_current_logical_core|lfds711_queue_umm_init_valid_on_current_logical_core]]''
* ''[[r7.1.1:function lfds711_ringbuffer_init_valid_on_current_logical_core|lfds711_ringbuffer_init_valid_on_current_logical_core]]''

Latest revision as of 20:16, 17 February 2017

Source File

└───liblfds711
    └───inc
        └───liblfds711
                lfds711_ringbuffer.h

Opaque Structure

struct lfds711_ringbuffer_element;

Alignment

No alignment requirements.

Notes

This structure represents the state of a ringbuffer element. It is published in the public header file so it can be allocated on the stack, embedded in user structures and passed to sizeof. The actual internal implementation is opaque and must not be touched.

See Also