Memory Usage

This guide describes how to configure and use the NoxTLS memory management system: system allocator vs. static buffer pool, bucket pools, configuration, and examples.

Overview

The NoxTLS library provides a configurable memory management system that can use either:

• System malloc/free (default) — Standard system memory allocation
• Static buffer pool — Pre-allocated buffer managed by the library

When static buffers are enabled, the pool can use one of three allocator strategies:

Mode	NOXTLS_STATIC_ALLOCATOR_MODE	Behavior
HYBRID (default)	NOXTLS_STATIC_ALLOCATOR_MODE_HYBRID	Fixed-size bucket pools for common allocation sizes; remaining buffer space is a fallback first-fit pool for larger or overflow allocations
BUCKETS	NOXTLS_STATIC_ALLOCATOR_MODE_BUCKETS	Bucket pools only; allocations that do not fit any bucket class fail
LEGACY	NOXTLS_STATIC_ALLOCATOR_MODE_LEGACY	Original single first-fit pool over the entire buffer (no buckets)

Bucket allocation is O(1) and avoids fragmentation for the size classes you configure. HYBRID is recommended for embedded TLS workloads where most allocations are small but occasional larger handshake buffers are still needed.

Configuration

Edit noxtls_config.h to enable static buffers and tune the allocator:

#define NOXTLS_USE_STATIC_BUFFERS 1
#define NOXTLS_STATIC_BUFFER_SIZE (64 * 1024)  /* 64KB default */

/* Default: try buckets first, then fallback pool */
#define NOXTLS_STATIC_ALLOCATOR_MODE NOXTLS_STATIC_ALLOCATOR_MODE_HYBRID

Bucket pool settings

Bucket classes are defined at compile time. Each class has a block size and a block count. At noxtls_mem_init(), the library lays out fixed blocks for every class from the start of your pool buffer; in HYBRID mode, any bytes left after bucket layout become the fallback pool.

Default configuration (from noxtls_config.h):

#define NOXTLS_MEM_BUCKET_COUNT 9U
#define NOXTLS_MEM_BUCKET_SIZES  32U, 64U, 128U, 256U, 512U, 1024U, 2048U, 4096U, 8192U
#define NOXTLS_MEM_BUCKET_COUNTS 16U, 16U, 12U, 10U, 8U, 6U, 4U, 2U, 1U
#define NOXTLS_MEM_BUCKET_ALIGNMENT 8U

Sizing a pool buffer: ensure NOXTLS_STATIC_BUFFER_SIZE (or the buffer you pass to noxtls_mem_init()) is large enough for:

1. Every bucket block: (sizeof(header) + aligned_block_size) × count for each class
2. In HYBRID or LEGACY mode, additional space for the fallback first-fit allocator (including alignment padding)

If the buffer is too small, noxtls_mem_init() returns NOXTLS_RETURN_FAILED. Increase NOXTLS_STATIC_BUFFER_SIZE or reduce NOXTLS_MEM_BUCKET_COUNTS / NOXTLS_MEM_BUCKET_COUNT for tighter RAM budgets.

Choosing a mode:

• Use HYBRID when you want predictable small allocations plus occasional large TLS records or certificate buffers.
• Use BUCKETS when you want hard upper bounds on allocation size and can size every class explicitly (no fallback).
• Use LEGACY only when you need backward-compatible behavior identical to pre-0.2.56 static pools.

Usage with Static Buffers

Option 1: Provide Your Own Buffer

Supply a pre-allocated buffer to the library. All internal allocations then use this buffer instead of system malloc.

#include "noxtls_memory.h"

uint8_t my_buffer[64 * 1024];  /* 64KB static buffer */

int main(void) {
    /* Initialize with your buffer */
    noxtls_return_t rc = noxtls_mem_init(my_buffer, sizeof(my_buffer));
    if(rc != NOXTLS_RETURN_SUCCESS) {
        /* Handle error */
        return -1;
    }
    
    /* Use library functions - all malloc/free calls will use your buffer */
    /* ... your code ... */
    
    /* Cleanup when done */
    noxtls_mem_cleanup();
    
    return 0;
}

Option 2: Let Library Allocate Buffer

Pass NULL as the buffer and a size; the library allocates the pool internally (via system malloc). Useful when you want a fixed cap on NoxTLS heap usage without managing the buffer yourself.

#include "noxtls_memory.h"

int main(void) {
    /* Initialize with NULL - library will allocate buffer internally */
    noxtls_return_t rc = noxtls_mem_init(NULL, 128 * 1024);
    if(rc != NOXTLS_RETURN_SUCCESS) {
        /* Handle error */
        return -1;
    }
    
    /* Use library functions */
    /* ... your code ... */
    
    /* Cleanup - will free internally allocated buffer */
    noxtls_mem_cleanup();
    
    return 0;
}

Memory Statistics

You can query memory usage statistics at runtime (static-buffer mode):

#include "noxtls_memory.h"
#include <stdio.h>

size_t total_allocated, total_used, max_used;
if(noxtls_mem_get_stats(&total_allocated, &total_used, &max_used) == NOXTLS_RETURN_SUCCESS) {
    printf("Total allocated: %zu bytes\n", total_allocated);
    printf("Currently used: %zu bytes\n", total_used);
    printf("Peak usage: %zu bytes\n", max_used);
}

Bucket pool statistics

When bucket pools are enabled (BUCKETS or HYBRID), use noxtls_mem_get_bucket_stats() to inspect per-class utilization and fallback usage:

#include "noxtls_memory.h"
#include <stdio.h>

noxtls_mem_bucket_stats_t stats;
if(noxtls_mem_get_bucket_stats(&stats) == NOXTLS_RETURN_SUCCESS) {
    size_t i;
    printf("Allocator mode: %u\n", (unsigned)stats.allocator_mode);
    printf("Fallback used: %zu / peak %zu (pool size %zu)\n",
           stats.fallback_used, stats.fallback_max_used, stats.fallback_size);
    for(i = 0; i < stats.bucket_count; ++i) {
        const noxtls_mem_bucket_stat_t *b = &stats.buckets[i];
        printf("Bucket %zu: size=%zu total=%zu used=%zu free=%zu\n",
               i, b->block_size, b->total_blocks, b->used_blocks, b->free_blocks);
    }
}

Use these counters during bring-up to tune NOXTLS_MEM_BUCKET_SIZES and NOXTLS_MEM_BUCKET_COUNTS. If the fallback pool shows sustained high usage in HYBRID mode, add blocks to the matching bucket class or increase the overall buffer size.

Last Allocation Failure

After an API returns NOXTLS_RETURN_NOT_ENOUGH_MEMORY, query the allocator's most recent failure:

#include "noxtls_memory.h"
#include <stdio.h>

noxtls_mem_error_info_t error;

if(noxtls_mem_get_last_error(&error) == NOXTLS_RETURN_SUCCESS) {
    printf("allocation failed at %s:%u in %s\n",
           error.source_file != NULL ? error.source_file : "<unknown>",
           (unsigned)error.source_line,
           error.source_function != NULL ? error.source_function : "<unknown>");
    printf("requested=%zu, largest-block=%zu, additional=%zu\n",
           error.requested_bytes,
           error.largest_available_block,
           error.minimum_additional_bytes);
}

The record persists across successful allocations so cleanup cannot erase the evidence. Call noxtls_mem_clear_last_error() before an operation when you want to distinguish a new failure from an older one. The static allocator reports an exact contiguous-payload shortfall. A system allocator may report NOXTLS_MEM_SIZE_UNKNOWN because the host does not expose remaining heap capacity. The record is module-wide; concurrent callers must serialize diagnostic access if they need to associate a failure with a particular thread.

Embedded Heap Profiles

The unit-test build includes four algorithm profile executables with fixed static heap pools of 32, 64, 128, and 256 KiB. Run them with the normal all-tests script, or select only the profiles:

.\run_tests_all.ps1 -Filter "embedded_memory"

Every enabled hash, block/stream cipher variant, AEAD/MAC, DRBG, finite-field DH, RSA size, DSA size, modern curve, and supported ECC curve is exercised with a fresh pool. Output reports context-state bytes, allocator peak/live bytes, allocation count, cumulative requested bytes, and largest single request. A real pool exhaustion reports the allocation location and exact contiguous-payload shortfall from noxtls_mem_get_last_error().

Every configured Weierstrass ECC curve performs scalar multiplication. The curve profiles also include a full P-256 workflow (two public-key derivations, bidirectional ECDH, and ECDSA/SHA-256 sign/verify), X25519 and X448 key-agreement round trips, and Ed25519 and Ed448 public-key/sign/verify round trips. These operations run without injected failures, so any OOM result is caused by the selected embedded heap limit.

These profiles use the LEGACY first-fit allocator so the entire stated pool is available to the algorithm; allocator-policy behavior is covered separately by the LEGACY, BUCKETS, HYBRID, and system allocator tests. The pool limit covers NoxTLS heap allocations. state= reports explicit context storage separately; compiler stack-frame usage is not included in the heap cap.

P-256 flash and low-RAM modes

Two optional settings move the reusable P-256 generator data out of RAM and avoid the large ECDSA verification joint table:

-DNOXTLS_ECC_P256_FLASH_PRECOMPUTE=ON
-DNOXTLS_ECC_P256_LOW_RAM_VERIFY=ON

NOXTLS_ECC_P256_FLASH_PRECOMPUTE adds a 2048-byte constant affine generator comb table. Embedded linkers place this read-only data in flash/ROM. It replaces the 6528-byte allocator-backed P-256 fixed-base table.

NOXTLS_ECC_P256_LOW_RAM_VERIFY requires the flash table. It computes the generator side from flash and builds only a compact 512-byte table for the runtime public key. This replaces the 13056-byte joint table used by the speed-oriented verification path. The compact table is selected with a constant-time scan and is released after each operation.

In the 32 KiB MSVC embedded profile, enabling both settings reduced the complete P-256 key-generation, ECDH, ECDSA-sign, and ECDSA-verify workflow from a 26920-byte heap peak to 4200 bytes. The largest single allocation fell from 13056 bytes to 1632 bytes. Low-RAM verification performs more point operations and rebuilds the runtime public-key table, so it trades verification throughput for RAM.

Notes

• When NOXTLS_USE_STATIC_BUFFERS is 0 (default), all allocation functions use system malloc/free.
• When NOXTLS_USE_STATIC_BUFFERS is 1, all library malloc/free calls are routed to the static buffer allocator.
• In static-buffer mode, if noxtls_mem_init() is not called explicitly, the allocator lazily initializes on first allocation using noxtls_mem_init(NULL, 0) and NOXTLS_STATIC_BUFFER_SIZE.
• Bucket frees return blocks to their class free list; fallback frees use coalescing first-fit logic (LEGACY and HYBRID fallback only).
• The compatibility header (noxtls_memory_compat.h) automatically replaces malloc/free with noxtls_malloc / noxtls_free in library code.
• Application code can still use standard malloc/free if needed.