Lines Matching full:forwarding

136 DSA frame header, in order to reduce the autonomous packet forwarding overhead.
633   specific port to be in the forwarding vector. Ports that are unused by the
779 VLAN-unaware bridges). During forwarding and FDB lookup, a packet received on a
885 for incorrect forwarding decisions. In this case, all standalone ports may
899 Offloading the bridge forwarding plane is optional and handled by the methods
902 possible, but the packet forwarding will take place in software, and the ports
907 Concretely, a port starts offloading the forwarding plane of a bridge once it
911 autonomously forwarding (or flooding) received packets without CPU intervention.
914 have already been autonomously forwarded in the forwarding domain of the
916 switch ports part of the same tree ID to be part of the same bridge forwarding
917 domain (capable of autonomous forwarding to each other).
919 Offloading the TX forwarding process of a bridge is a distinct concept from
920 simply offloading its forwarding plane, and refers to the ability of certain
933 When the TX forwarding offload is enabled, the tag protocol driver is
947   By setting the ``tx_fwd_offload`` argument to true, the TX forwarding process
992   forwarding needs to take place in software), or the VLAN is installed to the
1002   Forwarding Database entry, the switch hardware should be programmed with the
1003   specified address in the specified VLAN Id in the forwarding database
1007   Forwarding Database entry, the switch hardware should be programmed to delete
1009   this port forwarding database
1020   specified address in the specified VLAN ID in the forwarding database
1026   this port forwarding database.