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

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_element}}
{{DISPLAYTITLE:struct lfds711_queue_umm_state}}
==Source File==
==Source File==
  └───liblfds711
  └───liblfds711
Line 7: Line 7:


==Opaque Structure==
==Opaque Structure==
  struct lfds711_queue_umm_element;
  struct lfds711_queue_umm_state;


==Alignment==
==Alignment==
Line 13: Line 13:


==Notes==
==Notes==
This structure represents the state of a queue 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.
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.


==See Also==
==See Also==
* [[r7.1.1:Queue (unbounded, many producer, many consumer)|Queue (unbounded, many producer, many consumer)]]
* [[r7.1.1:Queue (unbounded, many producer, many consumer)|Queue (unbounded, many producer, many consumer)]]
* ''[[r7.1.1:function lfds711_queue_umm_enqueue|lfds711_queue_umm_enqueue]]''
* ''[[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_queue_umm_dequeue|lfds711_queue_umm_dequeue]]''

Latest revision as of 20:16, 17 February 2017

Source File

└───liblfds711
    └───inc
        └───liblfds711
                lfds711_queue_umm.h

Opaque Structure

struct lfds711_queue_umm_state;

Alignment

Allocations must be LFDS711_PAL_ATOMIC_ISOLATION_IN_BYTES aligned.

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.

See Also