tools/testing/selftests/bpf/progs/test_ringbuf_n.c
Source file repositories/reference/linux-study-clean/tools/testing/selftests/bpf/progs/test_ringbuf_n.c
File Facts
- System
- Linux kernel
- Corpus path
tools/testing/selftests/bpf/progs/test_ringbuf_n.c- Extension
.c- Size
- 860 bytes
- Lines
- 48
- 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
linux/bpf.hsched.hunistd.hbpf/bpf_helpers.hbpf_misc.h
Detected Declarations
struct samplefunction test_ringbuf_n
Annotated Snippet
struct sample {
int pid;
long value;
char comm[16];
};
struct {
__uint(type, BPF_MAP_TYPE_RINGBUF);
} ringbuf SEC(".maps");
int pid = 0;
long value = 0;
SEC("fentry/" SYS_PREFIX "sys_getpgid")
int test_ringbuf_n(void *ctx)
{
int cur_pid = bpf_get_current_pid_tgid() >> 32;
struct sample *sample;
if (cur_pid != pid)
return 0;
sample = bpf_ringbuf_reserve(&ringbuf, sizeof(*sample), 0);
if (!sample)
return 0;
sample->pid = pid;
sample->value = value;
bpf_get_current_comm(sample->comm, sizeof(sample->comm));
bpf_ringbuf_submit(sample, 0);
return 0;
}
Annotation
- Immediate include surface: `linux/bpf.h`, `sched.h`, `unistd.h`, `bpf/bpf_helpers.h`, `bpf_misc.h`.
- Detected declarations: `struct sample`, `function test_ringbuf_n`.
- 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.