From: David Miller <davem@davemloft.net>
To: herbert@gondor.apana.org.au
Cc: akpm@linux-foundation.org, netdev@vger.kernel.org
Subject: Re: linkwatch bustage in git-net
Date: Wed, 09 May 2007 00:18:14 -0700 (PDT) [thread overview]
Message-ID: <20070509.001814.116354599.davem@davemloft.net> (raw)
In-Reply-To: <20070509071614.GA2138@gondor.apana.org.au>
From: Herbert Xu <herbert@gondor.apana.org.au>
Date: Wed, 9 May 2007 17:16:15 +1000
> The real problem here is a combination of factors. First of all e100
> does a netif_carrier_off in its open routine *before* the first call
> to dev_activate. This when combined with the wrap-around bug causes
> an infinitely delayed event for your NIC to be installed.
I noticed that behavior of e100 too.
> [NET] link_watch: Always schedule urgent events
>
> Urgent events may be delayed if we already have a non-urgent event
> queued for that device. This patch changes this by making sure that
> an urgent event is always looked at immediately.
>
> I've replaced the LW_RUNNING flag by LW_URGENT since whether work
> is scheduled is already kept track by the work queue system.
>
> The only complication is that we have to provide some exclusion for
> the setting linkwatch_nextevent which is available in the actual
> work function.
>
> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Thanks for working this out, applied and pushed to net-2.6.git
next prev parent reply other threads:[~2007-05-09 7:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-09 5:20 linkwatch bustage in git-net Andrew Morton
2007-05-09 5:31 ` Herbert Xu
2007-05-09 5:45 ` Herbert Xu
[not found] ` <20070508225153.d538f79c.akpm@linux-foundation.org>
2007-05-09 5:54 ` Herbert Xu
2007-05-09 5:58 ` Andrew Morton
2007-05-09 6:11 ` Andrew Morton
2007-05-09 6:22 ` David Miller
2007-05-09 7:16 ` Herbert Xu
2007-05-09 7:18 ` David Miller [this message]
2007-05-09 21:11 ` Andrew Morton
2007-05-09 21:39 ` David Miller
2007-05-09 21:45 ` Andrew Morton
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=20070509.001814.116354599.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--cc=herbert@gondor.apana.org.au \
--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).