tools/testing/selftests/drivers/net/mlxsw/spectrum-2/tc_flower_scale.sh

File Facts

System

Linux kernel

Corpus path

tools/testing/selftests/drivers/net/mlxsw/spectrum-2/tc_flower_scale.sh

Extension

.sh

Size

599 bytes

Lines

26

Domain

Support Tooling And Documentation

Bucket

tools

Inferred role

Support Tooling And Documentation: tools

Status

atlas-only

Why This File Exists

Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

• Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

Dependency Surface

• No C-style include directives detected by the generator.

Detected Declarations

• No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

# SPDX-License-Identifier: GPL-2.0
source ../tc_flower_scale.sh

tc_flower_get_target()
{
	local should_fail=$1; shift
	local max_cnts

	# The driver associates a counter with each tc filter, which means the
	# number of supported filters is bounded by the number of available
	# counters.
	max_cnts=$(devlink_resource_size_get counters flow)

	# Remove already allocated counters.
	((max_cnts -= $(devlink_resource_occ_get counters flow)))

	# Each rule uses two counters, for packets and bytes.
	((max_cnts /= 2))

	if ((! should_fail)); then
		echo $max_cnts
	else
		echo $((max_cnts + 1))
	fi
}

Annotation

• Atlas domain: Support Tooling And Documentation / tools.
• Implementation status: atlas-only.

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.