From: Stephen Hemminger <shemminger@osdl.org>
To: Thomas Glanzmann <sithglan@stud.uni-erlangen.de>
Cc: Daniel Drake <dsd@gentoo.org>, Bill Hoover <bill@luminescent.com>,
Bertrand Jacquin <beber@gna.org>,
micheleschi@libero.it, netdev@vger.kernel.org,
teppic74@hotmail.com
Subject: Re: sky2 1.3-rc1
Date: Fri, 5 May 2006 10:45:36 -0700 [thread overview]
Message-ID: <20060505104536.2baefa5e@localhost.localdomain> (raw)
In-Reply-To: <20060505173509.GK2757@cip.informatik.uni-erlangen.de>
On Fri, 5 May 2006 19:35:09 +0200
Thomas Glanzmann <sithglan@stud.uni-erlangen.de> wrote:
> Hello,
>
> > > http://developer.osdl.org/shemminger/prototypes/sky2-1.3-rc1.tar.bz2
>
> > v0.15:
> > 64 bytes from 10.0.0.138: icmp_seq=2 ttl=64 time=0.467 ms
>
> > v1.3-rc1:
> > 64 bytes from 10.0.0.138: icmp_seq=4 ttl=64 time=32.9 ms
>
> I can't confirm this. For me it is just perfect:
>
> 64 bytes from 89.106.66.1: icmp_seq=1 ttl=64 time=0.278 ms
>
> 0000:04:00.0 Ethernet controller: Marvell Technology Group Ltd.: Unknown device 4361 (rev 17)
>
> Thomas
What is happening is that if there is a misconfiguration and irq routing
is messed up (ie edge trigged). The driver will degenerate to polling every 100ms.
If your system is this misconfigured, then ACPI or the BIOS needs to be fixed
and the driver really only needs to work well enough to get the bug report out ;-)
The older driver was doing rewhacking the Transmit IRQ status timer,
so it would give a bogus transmit status interrupt and that was masking
issues.
next prev parent reply other threads:[~2006-05-05 18:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1146667951.3056.25.camel@fc5test.deadmoose.com>
2006-05-03 19:05 ` sky2 1.3-rc1 Stephen Hemminger
2006-05-05 14:34 ` Daniel Drake
2006-05-05 17:35 ` Thomas Glanzmann
2006-05-05 17:45 ` Stephen Hemminger [this message]
2006-05-05 18:42 ` Daniel Drake
2006-05-05 19:43 ` Stephen Hemminger
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=20060505104536.2baefa5e@localhost.localdomain \
--to=shemminger@osdl.org \
--cc=beber@gna.org \
--cc=bill@luminescent.com \
--cc=dsd@gentoo.org \
--cc=micheleschi@libero.it \
--cc=netdev@vger.kernel.org \
--cc=sithglan@stud.uni-erlangen.de \
--cc=teppic74@hotmail.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;
as well as URLs for NNTP newsgroup(s).