Skip to content

Commit

Permalink
lib: Document the unsafe datastack mempool
Browse files Browse the repository at this point in the history
  • Loading branch information
Josef 'Jeff' Sipek authored and villesavolainen committed Feb 6, 2019
1 parent 592652d commit 19d270a
Showing 1 changed file with 42 additions and 0 deletions.
42 changes: 42 additions & 0 deletions src/lib/mempool-unsafe-datastack.c
Expand Up @@ -3,6 +3,48 @@
#include "lib.h"
#include "mempool.h"

/*
* The unsafe datastack pool is a very thin wrapper around the datastack
* API. It is a simpler version of the datastack pool that does not do any
* sanity checking, it simply forwards the calls to the datastack API. It
* exists to allow some internal APIs to make datastack allocations via the
* pool API.
*
* Note to consumers: Consider using the (safe) datastack pool instead of
* this one.
*
* Implementation
* ==============
*
* Creation
* --------
*
* The unsafe datastack pool is created statically and therefore is
* available at any time after the datastack allocator is initialized.
*
* Allocation & Reallocation
* -------------------------
*
* The p_malloc() and p_realloc() calls get directed to t_malloc0() and
* t_try_realloc(), respectively. There is no additional per-allocation
* information to track.
*
* Freeing
* -------
*
* A no-op.
*
* Clearing
* --------
*
* A no-op.
*
* Destruction
* -----------
*
* It is not possible to destroy the unsafe datastack pool. Any attempt to
* unref the pool is a no-op.
*/

static const char *pool_unsafe_data_stack_get_name(pool_t pool);
static void pool_unsafe_data_stack_ref(pool_t pool);
Expand Down

0 comments on commit 19d270a

Please sign in to comment.