include/linux/union_find.h

File Facts

System

Linux kernel

Corpus path

include/linux/union_find.h

Extension

.h

Size

1167 bytes

Lines

42

Domain

Core OS

Bucket

Core Kernel Interface

Inferred role

Core OS: implementation source

Status

source implementation candidate

Why This File Exists

Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.

• Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
• 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 uf_node
• function uf_node_init

Annotated Snippet

struct uf_node {
	struct uf_node *parent;
	unsigned int rank;
};

/* This macro is used for static initialization of a union-find node. */
#define UF_INIT_NODE(node)	{.parent = &node, .rank = 0}

/**
 * uf_node_init - Initialize a union-find node
 * @node: pointer to the union-find node to be initialized
 *
 * This function sets the parent of the node to itself and
 * initializes its rank to 0.
 */
static inline void uf_node_init(struct uf_node *node)
{
	node->parent = node;
	node->rank = 0;
}

/* find the root of a node */
struct uf_node *uf_find(struct uf_node *node);

/* Merge two intersecting nodes */
void uf_union(struct uf_node *node1, struct uf_node *node2);

#endif /* __LINUX_UNION_FIND_H */

Annotation

• Detected declarations: `struct uf_node`, `function uf_node_init`.
• Atlas domain: Core OS / Core Kernel Interface.
• 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.