tools/perf/util/sharded_mutex.c
Source file repositories/reference/linux-study-clean/tools/perf/util/sharded_mutex.c
File Facts
- System
- Linux kernel
- Corpus path
tools/perf/util/sharded_mutex.c- Extension
.c- Size
- 684 bytes
- Lines
- 34
- 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
sharded_mutex.hstdlib.h
Detected Declarations
function sharded_mutex__delete
Annotated Snippet
// SPDX-License-Identifier: GPL-2.0
#include "sharded_mutex.h"
#include <stdlib.h>
struct sharded_mutex *sharded_mutex__new(size_t num_shards)
{
struct sharded_mutex *result;
size_t size;
unsigned int bits;
for (bits = 0; ((size_t)1 << bits) < num_shards; bits++)
;
size = sizeof(*result) + sizeof(struct mutex) * (1 << bits);
result = malloc(size);
if (!result)
return NULL;
result->cap_bits = bits;
for (size_t i = 0; i < ((size_t)1 << bits); i++)
mutex_init(&result->mutexes[i]);
return result;
}
void sharded_mutex__delete(struct sharded_mutex *sm)
{
for (size_t i = 0; i < ((size_t)1 << sm->cap_bits); i++)
mutex_destroy(&sm->mutexes[i]);
free(sm);
}
Annotation
- Immediate include surface: `sharded_mutex.h`, `stdlib.h`.
- Detected declarations: `function sharded_mutex__delete`.
- 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.