Difference between pages "r7.1.1:Struct libbenchmark topology state" and "r7.1.1:Struct libshared memory 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 libbenchmark_topology_state}}
{{DISPLAYTITLE:struct libshared_memory_state}}
==Source File==
==Source File==
  └── test_and_benchmark
  └── test_and_benchmark
     └── libbenchmark
     └── libshared
         └── inc
         └── inc
             └── libbenchmark
             └── libshared
                 └── libbenchmark_topology.h
                 └── libshared_memory.h


==Opaque Structure==
==Opaque Structure==
  struct libbenchmark_topology_state;
  struct libshared_memory_state;


==Alignment==
==Alignment==
Line 14: Line 14:


==Notes==
==Notes==
This structure represents a topology tree.
This structure is used to manage user-provided memory aloocations. 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.
 
Users never themselves allocate this structure, rather, it is presented to their implementation of the abstraction layer function ''libbenchmark_pal_populate_topology''.


==See Also==
==See Also==
* [[r7.1.1:Porting Guide (libbenchmark)|Porting Guide (libbenchmark)]]
* [[r7.1.1:Usage Guide (libshared)|Usage Guide (libshared)]]
* ''[[r7.1.1:function libbenchmark_pal_populate_topology|libbenchmark_pal_populate_topology]]''

Latest revision as of 20:16, 17 February 2017

Source File

└── test_and_benchmark
    └── libshared
        └── inc
            └── libshared
                └── libshared_memory.h

Opaque Structure

struct libshared_memory_state;

Alignment

Allocations must be LFDS711_PAL_ATOMIC_ISOLATION_IN_BYTES aligned.

Notes

This structure is used to manage user-provided memory aloocations. 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