Lines Matching full:ports

100     # brought up manually before the user ports.
112     # brought up manually before the user ports.
123     # add ports to bridge
138     # brought up manually before the user ports.
152     # add ports to bridge
182     # brought up manually before the user ports.
199     # add ports to bridges
204     # tag traffic on ports
225     # brought up manually before the user ports.
240     # add ports to bridge
246     # tag traffic on ports
265     # brought up manually before the user ports.
281     # add ports to bridges
287     # tag traffic on ports
367 Affinity of user ports to CPU ports
372 may permit the use of 2 or more ports connected to the host, for an increase in
375 DSA can make use of multiple CPU ports in two ways. First, it is possible to
378 custom policies of static load balancing between user ports, by spreading the
379 affinities according to the available CPU ports.
381 Secondly, it is possible to perform load balancing between CPU ports on a per
382 packet basis, rather than statically assigning user ports to CPU ports.
385 on the CPU ports facing the physical DSA conduits that constitute the LAG slave
388 To make use of multiple CPU ports, the firmware (device tree) description of
389 the switch must mark all the links between CPU ports and their DSA conduits
417     # CPU ports in LAG, using explicit assignment of the DSA conduit
429     # CPU ports in LAG, relying on implicit migration of the DSA conduit
437 Notice that in the case of CPU ports under a LAG, the use of the
440 and migrates all user ports to the new upper of ``eth0``, ``bond0``. Similarly,
441 when ``bond0`` is destroyed using ``RTM_DELLINK``, DSA migrates the user ports
446 In a setup with more than 2 physical CPU ports, it is therefore possible to mix