drivers/md/dm-vdo/indexer/funnel-requestqueue.h

File Facts

System

Linux kernel

Corpus path

drivers/md/dm-vdo/indexer/funnel-requestqueue.h

Extension

.h

Size

916 bytes

Lines

32

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

• indexer.h

Detected Declarations

• struct uds_request_queue

Annotated Snippet

#ifndef UDS_REQUEST_QUEUE_H
#define UDS_REQUEST_QUEUE_H

#include "indexer.h"

/*
 * A simple request queue which will handle new requests in the order in which they are received,
 * and will attempt to handle requeued requests before new ones. However, the nature of the
 * implementation means that it cannot guarantee this ordering; the prioritization is merely a
 * hint.
 */

struct uds_request_queue;

typedef void (*uds_request_queue_processor_fn)(struct uds_request *);

int __must_check uds_make_request_queue(const char *queue_name,
					uds_request_queue_processor_fn processor,
					struct uds_request_queue **queue_ptr);

void uds_request_queue_enqueue(struct uds_request_queue *queue,
			       struct uds_request *request);

void uds_request_queue_finish(struct uds_request_queue *queue);

#endif /* UDS_REQUEST_QUEUE_H */

Annotation

• Immediate include surface: `indexer.h`.
• Detected declarations: `struct uds_request_queue`.
• 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.