netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: netdev@vger.kernel.org
Subject: A Networking Puzzle
Date: Tue, 12 Sep 2006 09:43:28 -0500	[thread overview]
Message-ID: <4506C790.1020007@lwfinger.net> (raw)

Jeff,

I need help with a networking problem and I hope you can direct me to a guru.

As part of the changes in the bcm43xx driver just prior to 2.6.18, some sections 
that are executed periodically were made preemptible to reduce latency. For the 
most part, the effort was successful; however there are intermittent failures on 
certain systems. The code in question is run once per minute, with failures only 
after 6-10 hours when they occur. Fortunately for testing purposes, my system is 
one that is affected by this problem. In addition, I could tweak the code to run 
the problem section once per second. This way, I could experiment with the code 
and I think I found the problem.

In the code setting up the preemptive work, the relevant section has the following:

	...
	mutex_lock
	netif_stop_queue
	synchronize_net
	....

With this structure, a netdev watchdog tx timeout will happen every few hundred 
passes through the code, even if the timeout is set to 30 sec. From 
experimentation, I know that if the synchronize_net call is removed, or if it 
comes before the netif_stop_queue, I no longer get the errors. Of course it is 
possible that my changes just reduce the error rate to a level that I don't see 
it with limited testing. I'm hoping that an expert can explain which of these 
two changes might be correct, or what should be done.

Thanks,

Larry

                 reply	other threads:[~2006-09-12 14:43 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=4506C790.1020007@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=jgarzik@pobox.com \
    --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 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).