From: jaypee@hotpop.com
To: linux-mips <linux-mips@linux-mips.org>
Cc: tnt@246tNt.com
Subject: Au1xxx ethernet race condition?
Date: Thu, 11 Aug 2005 08:35:29 +0000 [thread overview]
Message-ID: <1123749337l.30285l.5l@cavan> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
While preforming network soak test on our au1550 based board, I noticed
lots of netdev timeout messages.
If I increased the ETH_TX_TIMEOUT to 5*HZ from HZ/4, I can see that
traffic does stop until the watchdog barks.
However if I print out the TX DMA status at this stage all the buffers
are ready to use.
My theory as to why this occurs is that in au1000_tx there is a race
condition.
If a tx_done interrupt for the last tx buffer occurs between reading
buff_stat (line 1905, au1000_eth.c) and calling netif_stop_queue then
the queue won't get woken until the watchdog barks.
I inserted a local_irq_save() at line 1903 and a local_irq_restore()
at line 1915 and that seems to have fixed the problem. (Been running
for half an hour with no netdev timeouts).
I'm sure this is overkill. Can anyone else confirm?
a) they see the problem
b) that there is a better solution
As an aside, the network stack for the 2.6 kernel is pretty slow, as
large 32k udp pckts don't use anywhere near the amount of cycles that
1.5k udp pckts do.
Suggests to me that it is the udp/ip path that is the bottleneck.
Just had a look at the mailing list and it looks like sylvain is
having a similar problem. Can you try this fix and see if it removes
your netdev tx timeouts sylvain?
thankx
- --
mailto:jaypee@hotpop.com
http://www.jaypee.org.uk
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFC+w3ZZDxnKy3oOpYRAsPKAKCe5R6qBsmMDyBY1w/MvoL1CvabvwCdEz9g
xFXbK05i7hD0PAYwotk2+u0=
=W7tS
-----END PGP SIGNATURE-----
next reply other threads:[~2005-08-11 8:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-11 8:35 jaypee [this message]
2005-08-11 9:05 ` Au1xxx ethernet race condition? Jerry
2005-08-11 9:25 ` jaypee
2005-08-11 9:28 ` jaypee
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=1123749337l.30285l.5l@cavan \
--to=jaypee@hotpop.com \
--cc=linux-mips@linux-mips.org \
--cc=tnt@246tNt.com \
/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