tools/testing/selftests/drivers/net/mlxsw/spectrum/rif_counter_scale.sh

File Facts

System

Linux kernel

Corpus path

tools/testing/selftests/drivers/net/mlxsw/spectrum/rif_counter_scale.sh

Extension

.sh

Size

736 bytes

Lines

35

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 ../rif_counter_scale.sh

rif_counter_get_target()
{
	local should_fail=$1; shift
	local max_cnts
	local max_rifs
	local target

	max_rifs=$(devlink_resource_size_get rifs)
	max_cnts=$(devlink_resource_size_get counters rif)

	# Remove already allocated RIFs.
	((max_rifs -= $(devlink_resource_occ_get rifs)))

	# 10 KVD slots per counter, ingress+egress counters per RIF
	((max_cnts /= 20))

	# Pointless to run the overflow test if we don't have enough RIFs to
	# host all the counters.
	if ((max_cnts > max_rifs && should_fail)); then
		echo 0
		return
	fi

	target=$((max_rifs < max_cnts ? max_rifs : max_cnts))

	if ((! should_fail)); then
		echo $target
	else
		echo $((target + 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.