diff options
author | Vladimir Oltean | 2019-05-05 12:19:27 +0200 |
---|---|---|
committer | David S. Miller | 2019-05-06 06:52:42 +0200 |
commit | 227d07a07ef126272ea2eed97fd136cd7a803d81 (patch) | |
tree | d5004e1438e81abf29266b349005ae3a945f7e72 /kernel/hung_task.c | |
parent | net: dsa: Add a private structure pointer to dsa_port (diff) | |
download | kernel-qcow2-linux-227d07a07ef126272ea2eed97fd136cd7a803d81.tar.gz kernel-qcow2-linux-227d07a07ef126272ea2eed97fd136cd7a803d81.tar.xz kernel-qcow2-linux-227d07a07ef126272ea2eed97fd136cd7a803d81.zip |
net: dsa: sja1105: Add support for traffic through standalone ports
In order to support this, we are creating a make-shift switch tag out of
a VLAN trunk configured on the CPU port. Termination of normal traffic
on switch ports only works when not under a vlan_filtering bridge.
Termination of management (PTP, BPDU) traffic works under all
circumstances because it uses a different tagging mechanism
(incl_srcpt). We are making use of the generic CONFIG_NET_DSA_TAG_8021Q
code and leveraging it from our own CONFIG_NET_DSA_TAG_SJA1105.
There are two types of traffic: regular and link-local.
The link-local traffic received on the CPU port is trapped from the
switch's regular forwarding decisions because it matched one of the two
DMAC filters for management traffic.
On transmission, the switch requires special massaging for these
link-local frames. Due to a weird implementation of the switching IP, by
default it drops link-local frames that originate on the CPU port.
It needs to be told where to forward them to, through an SPI command
("management route") that is valid for only a single frame.
So when we're sending link-local traffic, we are using the
dsa_defer_xmit mechanism.
Signed-off-by: Vladimir Oltean <olteanv@gmail.com>
Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'kernel/hung_task.c')
0 files changed, 0 insertions, 0 deletions