drivers/net/ethernet/mellanox/mlx5/core/en/tc/act/ptype.c

File Facts

System

Linux kernel

Corpus path

drivers/net/ethernet/mellanox/mlx5/core/en/tc/act/ptype.c

Extension

.c

Size

682 bytes

Lines

27

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

• act.h
• en/tc_priv.h

Detected Declarations

• function tc_act_parse_ptype

Annotated Snippet

// SPDX-License-Identifier: GPL-2.0 OR Linux-OpenIB
// Copyright (c) 2021, NVIDIA CORPORATION & AFFILIATES. All rights reserved.

#include "act.h"
#include "en/tc_priv.h"

static int
tc_act_parse_ptype(struct mlx5e_tc_act_parse_state *parse_state,
		   const struct flow_action_entry *act,
		   struct mlx5e_priv *priv,
		   struct mlx5_flow_attr *attr)
{
	struct netlink_ext_ack *extack = parse_state->extack;

	if (act->ptype != PACKET_HOST) {
		NL_SET_ERR_MSG_MOD(extack, "skbedit ptype is only supported with type host");
		return -EOPNOTSUPP;
	}

	parse_state->ptype_host = true;
	return 0;
}

struct mlx5e_tc_act mlx5e_tc_act_ptype = {
	.parse_action = tc_act_parse_ptype,
};

Annotation

• Immediate include surface: `act.h`, `en/tc_priv.h`.
• Detected declarations: `function tc_act_parse_ptype`.
• 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.