From: Timur Tabi <timur@codeaurora.org>
To: netdev <netdev@vger.kernel.org>
Subject: Need help parsing dropwatch results
Date: Tue, 18 Oct 2016 18:57:24 -0500 [thread overview]
Message-ID: <5806B6E4.1050004@codeaurora.org> (raw)
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.
reply other threads:[~2016-10-18 23:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5806B6E4.1050004@codeaurora.org \
--to=timur@codeaurora.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.