From: Florian Fainelli <f.fainelli@gmail.com>
To: Timur Tabi <timur@codeaurora.org>, netdev <netdev@vger.kernel.org>
Subject: Re: How can I test ndo_tx_timeout()?
Date: Thu, 26 May 2016 14:34:00 -0700 [thread overview]
Message-ID: <57476BC8.5060706@gmail.com> (raw)
In-Reply-To: <CAOZdJXWDp1VzCtu0PQp9m_62_2sXLZeiZqsmqb_GP71Bn1bMuQ@mail.gmail.com>
On 05/26/2016 01:40 PM, Timur Tabi wrote:
> Is there an easy way to test my driver's response to a
> ndo_tx_timeout() call? That is, force dev_watchdog() to think that a
> timeout has occurred?
>
One way to do this could be to never reclaim the SKBs you just
transmitted which could be achieved by disabling the TX completion
interrupt permanently for instance. Alternatively you might stop your tx
queue, avoid checking for this condition (netif_tx_queue_stopped..) and
still try to push SKBs and transmit them, combining the two should be
fairly effective.
There could be better ways to test that, though these would at least try
to reproduce real world scenarios where transmit flow control is broken.
--
Florian
next prev parent reply other threads:[~2016-05-26 21:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-26 20:40 How can I test ndo_tx_timeout()? Timur Tabi
2016-05-26 21:34 ` Florian Fainelli [this message]
2016-05-26 22:33 ` Timur Tabi
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=57476BC8.5060706@gmail.com \
--to=f.fainelli@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=timur@codeaurora.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 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).