tools/testing/selftests/drivers/net/mlxsw/router_bridge_lag.sh
Source file repositories/reference/linux-study-clean/tools/testing/selftests/drivers/net/mlxsw/router_bridge_lag.sh
File Facts
- System
- Linux kernel
- Corpus path
tools/testing/selftests/drivers/net/mlxsw/router_bridge_lag.sh- Extension
.sh- Size
- 786 bytes
- Lines
- 51
- 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
#!/bin/bash
# SPDX-License-Identifier: GPL-2.0
# Test enslavement to LAG with a clean slate.
# See $lib_dir/router_bridge_lag.sh for further details.
ALL_TESTS="
config_devlink_reload
config_enslave_h1
config_enslave_h2
config_enslave_h3
config_enslave_h4
config_enslave_swp1
config_enslave_swp2
config_enslave_swp3
config_enslave_swp4
config_wait
ping_ipv4
ping_ipv6
"
config_devlink_reload()
{
log_info "Devlink reload"
devlink_reload
}
config_enslave_h1()
{
config_enslave $h1 lag1
}
config_enslave_h2()
{
config_enslave $h2 lag4
}
config_enslave_h3()
{
config_enslave $h3 lag4
}
config_enslave_h4()
{
config_enslave $h4 lag1
}
lib_dir=$(dirname $0)/../../../net/forwarding
EXTRA_SOURCE="source $lib_dir/devlink_lib.sh"
source $lib_dir/router_bridge_lag.sh
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.