tools/testing/selftests/bpf/libarena/include/libarena/spmc.h

File Facts

System

Linux kernel

Corpus path

tools/testing/selftests/bpf/libarena/include/libarena/spmc.h

Extension

.h

Size

592 bytes

Lines

28

Domain

Support Tooling And Documentation

Bucket

tools

Inferred role

Support Tooling And Documentation: implementation source

Status

source implementation candidate

Why This File Exists

Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

• Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• No C-style include directives detected by the generator.

Detected Declarations

• struct spmc_arr
• struct spmc_arr
• struct spmc

Annotated Snippet

struct spmc_arr {
	u64 __arena *data;
	u64 order;
};

struct spmc {
	volatile struct spmc_arr __arena *cur;
	volatile u64 top;
	volatile u64 bottom;
	struct spmc_arr arr[SPMC_ARR_ORDERS];
};

int spmc_owned_add(struct spmc __arena *spmc, u64 val);
int spmc_owned_remove(struct spmc __arena *spmc, u64 *val);
int spmc_steal(struct spmc __arena *spmc, u64 *val);

struct spmc __arena *spmc_create(void);
int spmc_destroy(struct spmc __arena *spmc);

Annotation

• Detected declarations: `struct spmc_arr`, `struct spmc_arr`, `struct spmc`.
• Atlas domain: Support Tooling And Documentation / tools.
• Implementation status: source implementation candidate.

Implementation Notes

• This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
• Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
• Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.