tools/testing/selftests/net/test_vxlan_vnifiltering.sh
Source file repositories/reference/linux-study-clean/tools/testing/selftests/net/test_vxlan_vnifiltering.sh
File Facts
- System
- Linux kernel
- Corpus path
tools/testing/selftests/net/test_vxlan_vnifiltering.sh- Extension
.sh- Size
- 21448 bytes
- Lines
- 607
- 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
function vxlan_vnifilter_datapath_mgroup
Annotated Snippet
#!/bin/bash
# SPDX-License-Identifier: GPL-2.0
# This test is for checking the VXLAN vni filtering api and
# datapath.
# It simulates two hypervisors running two VMs each using four network
# six namespaces: two for the HVs, four for the VMs. Each VM is
# connected to a separate bridge. The VM's use overlapping vlans and
# hence the separate bridge domain. Each vxlan device is a collect
# metadata device with vni filtering and hence has the ability to
# terminate configured vni's only.
# +--------------------------------+ +------------------------------------+
# | vm-11 netns | | vm-21 netns |
# | | | |
# |+------------+ +-------------+ | |+-------------+ +----------------+ |
# ||veth-11.10 | |veth-11.20 | | ||veth-21.10 | | veth-21.20 | |
# ||10.0.10.11/24 |10.0.20.11/24| | ||10.0.10.21/24| | 10.0.20.21/24 | |
# |+------|-----+ +|------------+ | |+-----------|-+ +---|------------+ |
# | | | | | | | |
# | | | | | +------------+ |
# | +------------+ | | | veth-21 | |
# | | veth-11 | | | | | |
# | | | | | +-----|------+ |
# | +-----|------+ | | | |
# | | | | | |
# +------------|-------------------+ +---------------|--------------------+
# +------------|-----------------------------------------|-------------------+
# | +-----|------+ +-----|------+ |
# | |vethhv-11 | |vethhv-21 | |
# | +----|-------+ +-----|------+ |
# | +---|---+ +---|--+ |
# | | br1 | | br2 | |
# | +---|---+ +---|--+ |
# | +---|----+ +---|--+ |
# | | vxlan1| |vxlan2| |
# | +--|-----+ +--|---+ |
# | | | |
# | | +---------------------+ | |
# | | |veth0 | | |
# | +---------|172.16.0.1/24 -----------+ |
# | |2002:fee1::1/64 | |
# | hv-1 netns +--------|------------+ |
# +-----------------------------|--------------------------------------------+
# |
# +-----------------------------|--------------------------------------------+
# | hv-2 netns +--------|-------------+ |
# | | veth0 | |
# | +------| 172.16.0.2/24 |---+ |
# | | | 2002:fee1::2/64 | | |
# | | | | | |
# | | +----------------------+ | - |
# | | | |
# | +-|-------+ +--------|-+ |
# | | vxlan1 | | vxlan2 | |
# | +----|----+ +---|------+ |
# | +--|--+ +-|---+ |
# | | br1 | | br2 | |
# | +--|--+ +--|--+ |
# | +-----|-------+ +----|-------+ |
# | | vethhv-12 | |vethhv-22 | |
# | +------|------+ +-------|----+ |
# +-----------------|----------------------------|---------------------------+
# | |
# +-----------------|-----------------+ +--------|---------------------------+
# | +-------|---+ | | +--|---------+ |
# | | veth-12 | | | |veth-22 | |
# | +-|--------|+ | | +--|--------|+ |
# | | | | | | | |
# |+----------|--+ +---|-----------+ | |+-------|-----+ +|---------------+ |Annotation
- Detected declarations: `function vxlan_vnifilter_datapath_mgroup`.
- 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.