diff options
author | Maciej W. Rozycki <macro@linux-mips.org> | 2018-10-09 23:57:49 +0100 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2018-10-15 21:46:06 -0700 |
commit | 9f9a742db40f95f4dc20fc7293de4ea6ddb24e47 (patch) | |
tree | 5cbd5bcf3514e362f9f42275961b4880deb92fac /net/atm/pppoatm.c | |
parent | 61414f5ec9834df8aa4f55c90de16b71a3d6ca8d (diff) | |
download | linux-9f9a742db40f95f4dc20fc7293de4ea6ddb24e47.tar.bz2 |
FDDI: defza: Support capturing outgoing SMT traffic
DEC FDDIcontroller 700 (DEFZA) uses a Tx/Rx queue pair to communicate
SMT frames with adapter's firmware. Any SMT frame received from the RMC
via the Rx queue is queued back by the driver to the SMT Rx queue for
the firmware to process. Similarly the firmware uses the SMT Tx queue
to supply the driver with SMT frames which are queued back to the Tx
queue for the RMC to send to the ring.
When a network tap is attached to an FDDI interface handled by `defza'
any incoming SMT frames captured are queued to our usual processing of
network data received, which in turn delivers them to any listening
taps.
However the outgoing SMT frames produced by the firmware bypass our
network protocol stack and are therefore not delivered to taps. This in
turn means that taps are missing a part of network traffic sent by the
adapter, which may make it more difficult to track down network problems
or do general traffic analysis.
Call `dev_queue_xmit_nit' then in the SMT Tx path, having checked that
a network tap is attached, with a newly-created `dev_nit_active' helper
wrapping the usual condition used in the transmit path.
Signed-off-by: Maciej W. Rozycki <macro@linux-mips.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/atm/pppoatm.c')
0 files changed, 0 insertions, 0 deletions