Lines Matching refs:network
21 they configured/queried a switch port network device or a regular network
38 For each front-panel port, DSA will create specialized network devices which are
40 stack. These specialized network interfaces are referred to as "slave" network
56 Note that DSA does not currently create network interfaces for the "cpu" and
64 cannot really be used as proper network interfaces either, only the
84 Master network devices
87 Master network devices are regular, unmodified Linux network device drivers for
92 drivers. Such network devices are also often referred to as conduit network
106 Master network device (e.g.: e1000e):
133 -> locate per-port network device
134 -> invoke eth_type_trans() with the DSA slave network device
137 Past this point, the DSA slave network devices get delivered regular Ethernet
140 Slave network devices
143 Slave network devices created by DSA are stacked on top of their master network
144 device, each of these network interfaces will be responsible for being a
154 These slave network devices have custom net_device_ops and ethtool_ops function
158 Upon frame transmission from these slave network devices, DSA will look up which
159 switch tagging protocol is currently registered with these network devices, and
163 These frames are then queued for transmission using the master network device
171 Summarized, this is basically how DSA looks like from a network device
176 | CPU network device (eth0)|
219 master network device this switch tree is attached to needs to be referenced
221 dsa_switch_tree: structure assigned to the master network device under
229 dsa_switch_tree as a backpointer, slave network devices, master network device,
242 it will register the entire DSA switch tree attached to a master network device
259 Lack of CPU/DSA network devices
262 DSA does not currently create slave network devices for the CPU or DSA ports, as
277 Once a master network device is configured to use DSA (dev->dsa_ptr becomes
278 non-NULL), and the switch behind it expects a tagging protocol, this network
285 Slave network devices check that the master network device is UP before allowing
286 you to administratively bring UP these slave network devices. A common
287 configuration mistake is forgetting to bring UP the master network device first.
302 Slave network devices exposed by DSA may or may not be interfacing with PHY
334 of per-port slave network devices. Since DSA primarily deals with
386 configure the switch to separate all network interfaces from each other, that
424 - adjust_link: Function invoked by the PHY library when a slave network device
443 return their values. DSA overlays slave network devices general statistics:
444 RX/TX counters from the network device, with switch driver specific statistics
450 function may, for certain implementations also query the master network device
492 - port_enable: function invoked by the DSA slave network device ndo_open
498 - port_disable: function invoked by the DSA slave network device ndo_close
584 http://permalink.gmane.org/gmane.linux.network/329848
593 http://comments.gmane.org/gmane.linux.network/345803
613 http://comments.gmane.org/gmane.linux.network/365657
615 http://comments.gmane.org/gmane.linux.network/365510