net/dsa/conduit.h

File Facts

System

Linux kernel

Corpus path

net/dsa/conduit.h

Extension

.h

Size

726 bytes

Lines

23

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 dsa_port
• struct net_device
• struct netdev_lag_upper_info
• struct netlink_ext_ack

Annotated Snippet

#ifndef __DSA_CONDUIT_H
#define __DSA_CONDUIT_H

struct dsa_port;
struct net_device;
struct netdev_lag_upper_info;
struct netlink_ext_ack;

int dsa_conduit_setup(struct net_device *dev, struct dsa_port *cpu_dp);
void dsa_conduit_teardown(struct net_device *dev);
int dsa_conduit_lag_setup(struct net_device *lag_dev, struct dsa_port *cpu_dp,
			  struct netdev_lag_upper_info *uinfo,
			  struct netlink_ext_ack *extack);
void dsa_conduit_lag_teardown(struct net_device *lag_dev,
			      struct dsa_port *cpu_dp);
int __dsa_conduit_hwtstamp_validate(struct net_device *dev,
				    const struct kernel_hwtstamp_config *config,
				    struct netlink_ext_ack *extack);

#endif

Annotation

• Detected declarations: `struct dsa_port`, `struct net_device`, `struct netdev_lag_upper_info`, `struct netlink_ext_ack`.
• 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.