* Need help parsing dropwatch results
@ 2016-10-18 23:57 Timur Tabi
0 siblings, 0 replies; only message in thread
From: Timur Tabi @ 2016-10-18 23:57 UTC (permalink / raw)
To: netdev
Using iperf3 and dropwatch, I discovered that my EMAC driver is dropping
packets, a lot of them. This driver is based on an internal version
(written by someone else) that does not have this problem, so obviously
there's a bug in my driver. Unfortunately, I need help understanding
where in my driver the bug could be.
dropwatch display this:
3297 drops at net_tx_action+0 (0xffff000008aa1108)
3671 drops at net_tx_action+0 (0xffff000008aa1108)
4055 drops at net_tx_action+0 (0xffff000008aa1108)
3976 drops at net_tx_action+0 (0xffff000008aa1108)
3847 drops at net_tx_action+0 (0xffff000008aa1108)
3933 drops at net_tx_action+0 (0xffff000008aa1108)
3933 drops at net_tx_action+0 (0xffff000008aa1108)
1376 drops at net_tx_action+0 (0xffff000008aa1108)
Can someone tell me what "drops at net_tx_action+0" actually means? How
does a packet drop at net_tx_action() actually occur? Where in the
driver should I look for the problem?
--
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm
Technologies, Inc. Qualcomm Technologies, Inc. is a member of the
Code Aurora Forum, a Linux Foundation Collaborative Project.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2016-10-18 23:57 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-10-18 23:57 Need help parsing dropwatch results Timur Tabi
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).