Search results

Page title matches

• r6.1.0:Lfds610 stack use
  {{DISPLAYTITLE:r6.1.0:lfds610_stack_use}} /liblfds610/src/lfds610_stack/lfds610_stack_new.c
  670 bytes (97 words) - 14:07, 4 January 2015

Page text matches

• r6.1.0:Lfds610 stack use
  {{DISPLAYTITLE:r6.1.0:lfds610_stack_use}} /liblfds610/src/lfds610_stack/lfds610_stack_new.c
  670 bytes (97 words) - 14:07, 4 January 2015
• r6.1.0:Lfds610 stack new
  {{DISPLAYTITLE:r6.1.0:lfds610_stack_new}} /liblfds610/src/lfds610_stack/lfds610_stack_new.c
  1 KB (167 words) - 14:07, 4 January 2015
• r6.1.0:Lfds610 stack push
  {{DISPLAYTITLE:r6.1.0:lfds610_stack_push}} /liblfds610/src/lfds610_stack/lfds610_stack_push_pop.c
  1 KB (161 words) - 14:07, 4 January 2015
• r6.1.0:Lfds610 stack guaranteed push
  {{DISPLAYTITLE:r6.1.0:lfds610_stack_guaranteed_push}} /liblfds610/src/lfds610_stack/lfds610_stack_push_pop.c
  1 KB (154 words) - 14:07, 4 January 2015
• r6.1.0:Lfds610 stack query
  {{DISPLAYTITLE:r6.1.0:lfds610_stack_query}} /liblfds610/src/lfds610_stack/lfds610_stack_query.c
  3 KB (513 words) - 14:07, 4 January 2015
• r6.1.0:Lfds610 stack
  {{DISPLAYTITLE:r6.1.0:lfds610_stack}} /liblfds610/src/lfds610_stack/lfds610_stack_delete.c
  4 KB (629 words) - 14:07, 4 January 2015
• r6.1.0:Testing and Benchmarking Guide
  ...f the problems the tests try to detect are straightforward, but some are caused by race conditions. The more sensitive a test is, the more able it is to ...*1,000,000), the test is indeterminate; it is not possible to see if the ''lfds610_abstraction_incremement'' has been correctly implemented. Finally, if the
  16 KB (2,673 words) - 14:07, 4 January 2015
• r6.1.0:Lfds610 freelist
  {{DISPLAYTITLE:r6.1.0:lfds610_freelist}} /liblfds610/src/lfds610_freelist/lfds610_freelist_delete.c
  5 KB (823 words) - 14:07, 4 January 2015
• r6.1.0:Lfds610 ringbuffer
  {{DISPLAYTITLE:r6.1.0:lfds610_ringbuffer}} /liblfds610/src/lfds610_ringbuffer/lfds610_ringbuffer_delete.c
  10 KB (1,652 words) - 14:07, 4 January 2015
• r6.1.0:Upgrading Guide
  == User-Visible Changes == ...e method used to inline has changed; all inlining is now static (affecting LFDS610_INLINE define).
  3 KB (487 words) - 14:07, 4 January 2015
• r6.1.0:LFDS610 ALIGN
  {{DISPLAYTITLE:r6.1.0:LFDS610_ALIGN}} /liblfds610/inc/liblfds610.h
  2 KB (249 words) - 14:07, 4 January 2015
• r6.1.0:Introduction
  * [[r6.1.0:lfds610_freelist|Freelist]] * [[r6.1.0:lfds610_queue|Queue]]
  3 KB (417 words) - 14:07, 4 January 2015
• r6.1.0:Porting Guide (lfds)
  ...c keyword which controls the memory alignment of variables declared on the stack. ...compiler, otherwise we have the overhead of a function call every time we use one of these instructions and one of the points of using lock-free is perfo
  7 KB (954 words) - 14:07, 4 January 2015
• r6.1.0:Abstraction thread start
  ...d_state, unsigned int cpu, thread_function_t thread_function, void *thread_user_state ); ..._t under pthreads) and these are allocated on the heap or the stack by the user and the address of the variable is passed.
  4 KB (636 words) - 14:07, 4 January 2015
• r6.1.0:LFDS610 INLINE
  {{DISPLAYTITLE:r6.1.0:LFDS610_INLINE}} /liblfds610/inc/liblfds610.h
  1 KB (210 words) - 14:07, 4 January 2015