Lines Matching full:network
19 they configured/queried a switch port network device or a regular network
36 For each front-panel port, DSA will create specialized network devices which are
38 stack. These specialized network interfaces are referred to as "slave" network
54 Note that DSA does not currently create network interfaces for the "cpu" and
62 cannot really be used as proper network interfaces either, only the
101 ``needed_tailroom`` properties are also used to request from the network stack,
116 From the perspective of the network stack, all switches within the same DSA
129 the network stack sees. This can be seen with Marvell switch trees, where the
158 mockup driver, which can be attached to any network interface. The goal is that
159 any network interface should be capable of transmitting the same packet in the
167 ``struct net_device *dev`` represents the virtual DSA user network interface
182 virtual DSA user network interface corresponding to the physical front-facing
203 Master network devices
206 Master network devices are regular, unmodified Linux network device drivers for
211 drivers. Such network devices are also often referred to as conduit network
225 Master network device (e.g.: e1000e):
254 - locate per-port network device
255 - invoke ``eth_type_trans()`` with the DSA slave network device
258 Past this point, the DSA slave network devices get delivered regular Ethernet
261 Slave network devices
264 Slave network devices created by DSA are stacked on top of their master network
265 device, each of these network interfaces will be responsible for being a
275 These slave network devices have custom net_device_ops and ethtool_ops function
279 Upon frame transmission from these slave network devices, DSA will look up which
280 switch tagging protocol is currently registered with these network devices, and
284 These frames are then queued for transmission using the master network device
292 Summarized, this is basically how DSA looks like from a network device
353 the master network device this switch tree is attached to needs to be
356 - ``dsa_switch_tree``: structure assigned to the master network device under
364 a ``dsa_switch_tree`` as a backpointer, slave network devices, master network
373 Lack of CPU/DSA network devices
376 DSA does not currently create slave network devices for the CPU or DSA ports, as
391 Once a master network device is configured to use DSA (dev->dsa_ptr becomes
392 non-NULL), and the switch behind it expects a tagging protocol, this network
412 Slave network devices exposed by DSA may or may not be interfacing with PHY
444 of per-port slave network devices. As of today, the only SWITCHDEV objects
464 the non-user ports too, which are invisible to iproute2 because no network
513 configure the switch to separate all network interfaces from each other, that
541 - ``adjust_link``: Function invoked by the PHY library when a slave network device
560 return their values. DSA overlays slave network devices general statistics:
561 RX/TX counters from the network device, with switch driver specific statistics
567 function may, for certain implementations also query the master network device
609 - ``port_enable``: function invoked by the DSA slave network device ndo_open
615 - ``port_disable``: function invoked by the DSA slave network device ndo_close
736 and team drivers, which are modeled as virtual, stackable network interfaces.
779 Normally an MRP instance can be created on top of any network interface,
798 The Parallel Redundancy Protocol (PRP) is a network redundancy protocol which
806 health of the network and for discovery of other nodes.
809 instantiates a virtual, stackable network interface with two member ports.
812 of RedBox and QuadBox are not implemented (therefore, bridging a hsr network
843 http://comments.gmane.org/gmane.linux.network/365657