Lines Matching +full:out +full:- +full:ports
1 .. SPDX-License-Identifier: GPL-2.0
10 Copyright |copy| 2014-2015 Scott Feldman <sfeldma@gmail.com>
13 The Ethernet switch device driver model (switchdev) is an in-kernel driver
18 an example setup using a data-center-class switch ASIC chip. Other setups
19 with SR-IOV or soft switches, such as OVS, are possible.
24 User-space tools
27 +-------------------------------------------------------------------+
30 +--------------+-------------------------------+
34 +----------------------------------------------+
40 +--+----+----+----+----+----+---+ +-----+-----+
44 +--------------+----------------+ +-----------+
47 +-------------------------------------------------------------------+
49 +--------------+----------------+
51 | +----+ +--------+
54 +--|----|----+----+----+----+---+
59 front-panel ports
66 -------------
75 -------------
81 Switch Ports
82 ------------
94 There is (currently) no higher-level kernel object for the switch beyond the
111 The switch ID is used to locate ports on a switch and to know if aggregated
112 ports belong to the same switch.
119 Hard-coding of kernel netdev names within the driver is discouraged; let the
124 useful for dynamically-named ports where the device names its ports based on
126 into 4 10G ports, resulting in 4 port netdevs, the device can give a unique
133 is the port name or ID, and Z is the sub-port name or ID. For example, sw1p1s0
134 would be sub-port 0 on port 1 on switch 1.
143 the port netdev from being moved out of the default netns. A netns-aware
151 The port netdevs representing the physical switch ports can be organized into
152 higher-level switching constructs. The default construct is a standalone
153 router port, used to offload L3 forwarding. Two or more ports can be bonded
154 together to form a LAG. Two or more ports (or LAGs) can be bridged to bridge
155 L2 networks. VLANs can be applied to sub-divide L2 networks. L2-over-L3
156 tunnels can be built on ports. These constructs are built using standard Linux
157 tools such as the bridge driver, the bonding/team drivers, and netlink-based
168 ---------------------
176 - Static FDB entries installed on a bridge port
177 - Notification of learned/forgotten src mac/vlans from device
178 - STP state changes on the port
179 - VLAN flooding of multicast/broadcast and unknown unicast packets
252 the responsibility of the port driver/device to age out these entries. If the
262 notification will reset the FDB entry's last-used time to now. The driver
264 second. (The last-used time is visible using the bridge -s fdb option).
269 Internally or with a third-party STP protocol implementation (e.g. mstpd), the
270 bridge driver maintains the STP state for ports, and will notify the switch
277 and other IEEE 01:80:c2:xx:xx:xx link-local multicast packets can pass.
287 and unknown unicast packets to all ports in domain, if allowed by port's
288 current STP state. The switch driver, knowing which ports are within which
291 bridge should not reflood the packet to the same ports the device flooded,
295 forwarded by setting the skb->offload_fwd_mark bit. The bridge driver will mark
301 of ports scale in the L2 domain as the device is much more efficient at
315 traffic groups only to the configured ports.
318 ------------------
323 forwards the packet to the matching FIB entry's nexthop(s) egress ports.