drivers/md/dm-vdo/indexer/radix-sort.h

File Facts

System

Linux kernel

Corpus path

drivers/md/dm-vdo/indexer/radix-sort.h

Extension

.h

Size

797 bytes

Lines

27

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

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

Detected Declarations

• struct radix_sorter

Annotated Snippet

#ifndef UDS_RADIX_SORT_H
#define UDS_RADIX_SORT_H

/*
 * Radix sort is implemented using an American Flag sort, an unstable, in-place 8-bit radix
 * exchange sort. This is adapted from the algorithm in the paper by Peter M. McIlroy, Keith
 * Bostic, and M. Douglas McIlroy, "Engineering Radix Sort".
 *
 * http://www.usenix.org/publications/compsystems/1993/win_mcilroy.pdf
 */

struct radix_sorter;

int __must_check uds_make_radix_sorter(unsigned int count, struct radix_sorter **sorter);

void uds_free_radix_sorter(struct radix_sorter *sorter);

int __must_check uds_radix_sort(struct radix_sorter *sorter, const unsigned char *keys[],
				unsigned int count, unsigned short length);

#endif /* UDS_RADIX_SORT_H */

Annotation

• Detected declarations: `struct radix_sorter`.
• 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.