drivers/net/ethernet/marvell/prestera/prestera_flow.h

File Facts

System

Linux kernel

Corpus path

drivers/net/ethernet/marvell/prestera/prestera_flow.h

Extension

.h

Size

826 bytes

Lines

38

Domain

Driver Families

Bucket

drivers/net

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

• net/flow_offload.h

Detected Declarations

• struct prestera_port
• struct prestera_switch
• struct prestera_flow_block_binding
• struct prestera_flow_block

Annotated Snippet

struct prestera_flow_block_binding {
	struct list_head list;
	struct prestera_port *port;
	int span_id;
};

struct prestera_flow_block {
	struct list_head binding_list;
	struct prestera_switch *sw;
	struct net *net;
	struct prestera_acl_ruleset *ruleset_zero;
	struct flow_block_cb *block_cb;
	struct list_head template_list;
	struct {
		u32 prio_min;
		u32 prio_max;
		bool bound;
	} mall;
	unsigned int rule_count;
	bool ingress;
};

int prestera_flow_block_setup(struct prestera_port *port,
			      struct flow_block_offload *f);

#endif /* _PRESTERA_FLOW_H_ */

Annotation

• Immediate include surface: `net/flow_offload.h`.
• Detected declarations: `struct prestera_port`, `struct prestera_switch`, `struct prestera_flow_block_binding`, `struct prestera_flow_block`.
• Atlas domain: Driver Families / drivers/net.
• 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.