From: Jon Wikne <wikne@cheetah.uio.no>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: netdev@vger.kernel.org, Daniel Drake <dsd@gentoo.org>
Subject: Re: [RFT] sky2: transmit complete alternative
Date: Wed, 23 Aug 2006 12:06:00 +0200 [thread overview]
Message-ID: <44EC2888.7040005@cheetah.uio.no> (raw)
In-Reply-To: <20060822153841.1832f690@localhost.localdomain>
Stephen Hemminger wrote:
> Does the following get rid of the hang?
> --------
> Recode the transmit completion handling to avoid races between the hardware
> status report mechanism and the interrupt handler. Rather than relying on
> the index value in the status ring, read the chip register and cleanup
> all completed transmits.
>
> Reduce the transmit lock window smaller to allow more parallelism.
[ patch ]
I'm afraid not. :-(
1) The number of bytes before the hang occurs seems to have _decreased_
rather than the opposite. This observation is, however, a question
of statistics, and I have better such with the previous version.
2) Previously, the sequence /sbin/ifdown eth0 - /sbin/ifup eth0 made
the driver recover. Now, the latter of these commands hangs the
whole system. The recovery is now /sbin/ifdown eth0 - rmmod sky2
- modprobe sky2
-- Jon
next prev parent reply other threads:[~2006-08-23 10:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-21 12:41 sky2 driver - large files upload problem Jon Wikne
2006-08-21 13:18 ` Daniel Drake
2006-08-21 14:21 ` Jon Wikne
2006-08-21 16:51 ` Stephen Hemminger
2006-08-21 22:04 ` Jon Wikne
2006-08-21 23:36 ` Stephen Hemminger
2006-08-22 9:43 ` Jon Wikne
2006-08-22 22:38 ` [RFT] sky2: transmit complete alternative Stephen Hemminger
2006-08-23 10:06 ` Jon Wikne [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-08-30 23:22 Andrew Hall
[not found] ` <20060830163636.78fa1aed@localhost.localdomain>
2006-08-31 6:18 ` Andrew Hall
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=44EC2888.7040005@cheetah.uio.no \
--to=wikne@cheetah.uio.no \
--cc=dsd@gentoo.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@osdl.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).