include/net/dcbevent.h

File Facts

System

Linux kernel

Corpus path

include/net/dcbevent.h

Extension

.h

Size

766 bytes

Lines

40

Domain

Networking Core

Bucket

Sockets, Protocols, Packet Path, And Network Policy

Inferred role

Networking Core: implementation source

Status

source implementation candidate

Why This File Exists

Networking stack implementation surface: socket APIs, protocol dispatch, packet flow, routing, filtering, and network namespaces.

• Networking stack implementation surface: socket APIs, protocol dispatch, packet flow, routing, filtering, and network namespaces.
• 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 notifier_block
• enum dcbevent_notif_type
• function register_dcbevent_notifier
• function unregister_dcbevent_notifier
• function call_dcbevent_notifiers

Annotated Snippet

#ifndef _DCB_EVENT_H
#define _DCB_EVENT_H

struct notifier_block;

enum dcbevent_notif_type {
	DCB_APP_EVENT = 1,
};

#ifdef CONFIG_DCB
int register_dcbevent_notifier(struct notifier_block *nb);
int unregister_dcbevent_notifier(struct notifier_block *nb);
int call_dcbevent_notifiers(unsigned long val, void *v);
#else
static inline int
register_dcbevent_notifier(struct notifier_block *nb)
{
	return 0;
}

static inline int unregister_dcbevent_notifier(struct notifier_block *nb)
{
	return 0;
}

static inline int call_dcbevent_notifiers(unsigned long val, void *v)
{
	return 0;
}
#endif /* CONFIG_DCB */

#endif

Annotation

• Detected declarations: `struct notifier_block`, `enum dcbevent_notif_type`, `function register_dcbevent_notifier`, `function unregister_dcbevent_notifier`, `function call_dcbevent_notifiers`.
• Atlas domain: Networking Core / Sockets, Protocols, Packet Path, And Network Policy.
• 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.