From: Jeff Garzik <jgarzik@pobox.com>
To: Andrew Morton <akpm@osdl.org>
Cc: fedor@karpelevitch.net, abz@frogfoot.net, linux-kernel@vger.kernel.org
Subject: Re: possibly bug in 8139cp? (WAS Re: BUG: 2.4.23-pre3 + ifconfig)
Date: Mon, 08 Sep 2003 20:41:32 -0400 [thread overview]
Message-ID: <3F5D21BC.9020808@pobox.com> (raw)
In-Reply-To: <20030908170902.66f85c38.akpm@osdl.org>
Andrew Morton wrote:
> The only thing it can break is tg3, which appears to be placing a competing
> interpretation upon the handling of this flag.
Right, so, don't break tg3 :) The patch I posted doesn't do the
_and_set, which tg3 needs. netif_poll_{enable,disable} control whether
the net stack may call the dev->poll() function. tg3 asynchronously
disables polling, resets the phy and/or hardware, then enables polling
again.
I thought I had a check in there for when it was contending with
dev_close(), but I'll look again. The hardware/phy reset should
continue to occur regardless of dev_close() -- that's ok. During this
event, all rx/tx is already stopped anyway. So we can let ifdown/ifup
events occur in parallel... carefully. :)
Ideally we want to present a machine that's asynchronously managing its
power state and various functions. dev->open() and dev->close() events
become just two more "major events."
Jeff
prev parent reply other threads:[~2003-09-09 0:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-04 18:05 BUG: 2.4.23-pre3 + ifconfig Abraham van der Merwe
[not found] ` <200309071217.03470.fedor@karpelevitch.net>
2003-09-07 19:15 ` Abraham van der Merwe
[not found] ` <200309080943.26254.fedor@karpelevitch.net>
2003-09-08 16:46 ` possibly bug in 8139cp? (WAS Re: BUG: 2.4.23-pre3 + ifconfig) Abraham van der Merwe
2003-09-08 17:26 ` Jeff Garzik
2003-09-08 20:32 ` Andrew Morton
2003-09-08 23:59 ` Jeff Garzik
2003-09-09 0:09 ` Andrew Morton
2003-09-09 0:41 ` Jeff Garzik [this message]
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=3F5D21BC.9020808@pobox.com \
--to=jgarzik@pobox.com \
--cc=abz@frogfoot.net \
--cc=akpm@osdl.org \
--cc=fedor@karpelevitch.net \
--cc=linux-kernel@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