include/linux/dsa/ksz_common.h

File Facts

System

Linux kernel

Corpus path

include/linux/dsa/ksz_common.h

Extension

.h

Size

1212 bytes

Lines

54

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

• net/dsa.h

Detected Declarations

• struct ksz_deferred_xmit_work
• struct ksz_tagger_data
• struct ksz_skb_cb
• function Copyright
• function ksz_tagger_data

Annotated Snippet

struct ksz_deferred_xmit_work {
	struct dsa_port *dp;
	struct sk_buff *skb;
	struct kthread_work work;
};

struct ksz_tagger_data {
	void (*xmit_work_fn)(struct kthread_work *work);
	void (*hwtstamp_set_state)(struct dsa_switch *ds, bool on);
};

struct ksz_skb_cb {
	struct sk_buff *clone;
	unsigned int ptp_type;
	bool update_correction;
	u32 tstamp;
};

#define KSZ_SKB_CB(skb) \
	((struct ksz_skb_cb *)((skb)->cb))

static inline struct ksz_tagger_data *
ksz_tagger_data(struct dsa_switch *ds)
{
	return ds->tagger_data;
}

#endif /* _NET_DSA_KSZ_COMMON_H_ */

Annotation

• Immediate include surface: `net/dsa.h`.
• Detected declarations: `struct ksz_deferred_xmit_work`, `struct ksz_tagger_data`, `struct ksz_skb_cb`, `function Copyright`, `function ksz_tagger_data`.
• 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.