networking/dsa/dsa.rst

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
83 Master network devices
86 Master network devices are regular, unmodified Linux network device drivers for
91 drivers. Such network devices are also often referred to as conduit network
105 Master network device (e.g.: e1000e):
134         - locate per-port network device
135         - invoke ``eth_type_trans()`` with the DSA slave network device
138 Past this point, the DSA slave network devices get delivered regular Ethernet
141 Slave network devices
144 Slave network devices created by DSA are stacked on top of their master network
145 device, each of these network interfaces will be responsible for being a
155 These slave network devices have custom net_device_ops and ethtool_ops function
159 Upon frame transmission from these slave network devices, DSA will look up which
160 switch tagging protocol is currently registered with these network devices, and
164 These frames are then queued for transmission using the master network device
172 Summarized, this is basically how DSA looks like from a network device
177                 | CPU network device (eth0)|
222   the master network device this switch tree is attached to needs to be
225 - ``dsa_switch_tree``: structure assigned to the master network device under
233   a ``dsa_switch_tree`` as a backpointer, slave network devices, master network
250 Lack of CPU/DSA network devices
253 DSA does not currently create slave network devices for the CPU or DSA ports, as
268 Once a master network device is configured to use DSA (dev->dsa_ptr becomes
269 non-NULL), and the switch behind it expects a tagging protocol, this network
276 Slave network devices check that the master network device is UP before allowing
277 you to administratively bring UP these slave network devices. A common
278 configuration mistake is forgetting to bring UP the master network device first.
292 Slave network devices exposed by DSA may or may not be interfacing with PHY
324 of per-port slave network devices. Since DSA primarily deals with
368   configure the switch to separate all network interfaces from each other, that
396 - ``adjust_link``: Function invoked by the PHY library when a slave network device
415   return their values. DSA overlays slave network devices general statistics:
416   RX/TX counters from the network device, with switch driver specific statistics
422   function may, for certain implementations also query the master network device
464 - ``port_enable``: function invoked by the DSA slave network device ndo_open
470 - ``port_disable``: function invoked by the DSA slave network device ndo_close
585   http://comments.gmane.org/gmane.linux.network/365657
587   http://comments.gmane.org/gmane.linux.network/365510