tools/testing/selftests/bpf/progs/for_each_multi_maps.c
Source file repositories/reference/linux-study-clean/tools/testing/selftests/bpf/progs/for_each_multi_maps.c
File Facts
- System
- Linux kernel
- Corpus path
tools/testing/selftests/bpf/progs/for_each_multi_maps.c- Extension
.c- Size
- 919 bytes
- Lines
- 50
- 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
vmlinux.hbpf/bpf_helpers.h
Detected Declarations
struct callback_ctxfunction check_map_elemfunction test_pkt_access
Annotated Snippet
struct callback_ctx {
int output;
};
u32 data_output = 0;
int use_array = 0;
static __u64
check_map_elem(struct bpf_map *map, __u32 *key, __u64 *val,
struct callback_ctx *data)
{
data->output += *val;
return 0;
}
SEC("tc")
int test_pkt_access(struct __sk_buff *skb)
{
struct callback_ctx data;
data.output = 0;
if (use_array)
bpf_for_each_map_elem(&arraymap, check_map_elem, &data, 0);
else
bpf_for_each_map_elem(&hashmap, check_map_elem, &data, 0);
data_output = data.output;
return 0;
}
Annotation
- Immediate include surface: `vmlinux.h`, `bpf/bpf_helpers.h`.
- Detected declarations: `struct callback_ctx`, `function check_map_elem`, `function test_pkt_access`.
- 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.