diff options
| author | Vladimir Oltean <vladimir.oltean@nxp.com> | 2021-08-22 02:04:40 +0300 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2021-08-22 11:49:04 +0300 |
| commit | 37f299d98989bbac2b819eb5be97e093b817bb01 (patch) | |
| tree | b475c650a38893e8026b54b9ced6a5c3daa161a8 /Documentation/networking | |
| parent | 5702d94bd9019aaed2993628aa48b3c0acc5971f (diff) | |
| download | linux-37f299d98989bbac2b819eb5be97e093b817bb01.tar.xz | |
docs: net: dsa: remove references to struct dsa_device_ops::filter
This function has disappeared in commit edac6f6332d9 ("Revert "net: dsa:
Allow drivers to filter packets they can decode source port from"").
Also, since commit 4e50025129ef ("net: dsa: generalize overhead for
taggers that use both headers and trailers"), the next paragraph is no
longer true (it is still discouraged to do that, but it is now
supported, so no point in mentioning it). Delete.
Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'Documentation/networking')
| -rw-r--r-- | Documentation/networking/dsa/dsa.rst | 13 |
1 files changed, 0 insertions, 13 deletions
diff --git a/Documentation/networking/dsa/dsa.rst b/Documentation/networking/dsa/dsa.rst index 20baacf2bc5c..b64cb4068c13 100644 --- a/Documentation/networking/dsa/dsa.rst +++ b/Documentation/networking/dsa/dsa.rst @@ -200,19 +200,6 @@ receive all frames regardless of the value of the MAC DA. This can be done by setting the ``promisc_on_master`` property of the ``struct dsa_device_ops``. Note that this assumes a DSA-unaware master driver, which is the norm. -Hardware manufacturers are strongly discouraged to do this, but some tagging -protocols might not provide source port information on RX for all packets, but -e.g. only for control traffic (link-local PDUs). In this case, by implementing -the ``filter`` method of ``struct dsa_device_ops``, the tagger might select -which packets are to be redirected on RX towards the virtual DSA user network -interfaces, and which are to be left in the DSA master's RX data path. - -It might also happen (although silicon vendors are strongly discouraged to -produce hardware like this) that a tagging protocol splits the switch-specific -information into a header portion and a tail portion, therefore not falling -cleanly into any of the above 3 categories. DSA does not support this -configuration. - Master network devices ---------------------- |