drivers/md/dm-vdo/memory-alloc.h
Source file repositories/reference/linux-study-clean/drivers/md/dm-vdo/memory-alloc.h
File Facts
- System
- Linux kernel
- Corpus path
drivers/md/dm-vdo/memory-alloc.h- Extension
.h- Size
- 3441 bytes
- Lines
- 113
- Domain
- Driver Families
- Bucket
- drivers/md
- Inferred role
- Driver Families: implementation source
- Status
- source implementation candidate
Why This File Exists
Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
linux/cache.hlinux/io.hlinux/overflow.hpermassert.hthread-registry.h
Detected Declarations
function __alignof__
Annotated Snippet
#ifndef VDO_MEMORY_ALLOC_H
#define VDO_MEMORY_ALLOC_H
#include <linux/cache.h>
#include <linux/io.h> /* for PAGE_SIZE */
#include <linux/overflow.h>
#include "permassert.h"
#include "thread-registry.h"
/* Custom memory allocation function that tracks memory usage */
int __must_check vdo_allocate_memory(size_t size, size_t align, const char *what, void *ptr);
/*
* Allocate one or more elements of the indicated type, logging an error if the allocation fails.
* The memory will be zeroed.
*
* @COUNT: The number of objects to allocate
* @WHAT: What is being allocated (for error logging)
* @PTR: A pointer to hold the allocated memory
*
* Return: VDO_SUCCESS or an error code
*/
#define vdo_allocate(COUNT, WHAT, PTR) \
vdo_allocate_memory(size_mul((COUNT), sizeof(typeof(**(PTR)))), \
__alignof__(typeof(**(PTR))), WHAT, PTR)
/*
* Allocate a structure with a flexible array member, with a specified number of elements, logging
* an error if the allocation fails. The memory will be zeroed.
*
* @COUNT: The number of objects to allocate
* @FIELD: The flexible array field at the end of the structure
* @WHAT: What is being allocated (for error logging)
* @PTR: A pointer to hold the allocated memory
*
* Return: VDO_SUCCESS or an error code
*/
#define vdo_allocate_extended(COUNT, FIELD, WHAT, PTR) \
vdo_allocate_memory(struct_size(*(PTR), FIELD, (COUNT)), \
__alignof__(typeof(**(PTR))), \
WHAT, \
(PTR))
/*
* Allocate memory starting on a cache line boundary, logging an error if the allocation fails. The
* memory will be zeroed.
*
* @size: The number of bytes to allocate
* @what: What is being allocated (for error logging)
* @ptr: A pointer to hold the allocated memory
*
* Return: VDO_SUCCESS or an error code
*/
static inline int __must_check vdo_allocate_cache_aligned(size_t size, const char *what, void *ptr)
{
return vdo_allocate_memory(size, L1_CACHE_BYTES, what, ptr);
}
/*
* Allocate one element of the indicated type immediately, failing if the required memory is not
* immediately available.
*
* @size: The number of bytes to allocate
* @what: What is being allocated (for error logging)
*
* Return: pointer to the memory, or NULL if the memory is not available.
*/
void *__must_check vdo_allocate_memory_nowait(size_t size, const char *what);
int __must_check vdo_reallocate_memory(void *ptr, size_t old_size, size_t size,
const char *what, void *new_ptr);
int __must_check vdo_duplicate_string(const char *string, const char *what,
char **new_string);
/* Free memory allocated with vdo_allocate(). */
void vdo_free(void *ptr);
static inline void *__vdo_forget(void **ptr_ptr)
{
void *ptr = *ptr_ptr;
*ptr_ptr = NULL;
return ptr;
}
/*
* Null out a pointer and return a copy to it. This macro should be used when passing a pointer to
* a function for which it is not safe to access the pointer once the function returns.
Annotation
- Immediate include surface: `linux/cache.h`, `linux/io.h`, `linux/overflow.h`, `permassert.h`, `thread-registry.h`.
- Detected declarations: `function __alignof__`.
- Atlas domain: Driver Families / drivers/md.
- 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.