From: Auke Kok <auke-jan.h.kok@intel.com>
To: "Robin H. Johnson" <robbat2@gentoo.org>
Cc: Auke Kok <auke-jan.h.kok@intel.com>, Pavel Machek <pavel@ucw.cz>,
linux-kernel@vger.kernel.org
Subject: Re: e1000/ICH8LAN weirdness - no ethtool link until initially forced up
Date: Tue, 07 Nov 2006 14:32:32 -0800 [thread overview]
Message-ID: <45510980.2040808@intel.com> (raw)
In-Reply-To: <20061107213138.GA16523@curie-int.orbis-terrarum.net>
Robin H. Johnson wrote:
> On Tue, Nov 07, 2006 at 07:51:22AM -0800, Auke Kok wrote:
>>> I think you should cc e1000 maintainers, and perhaps provide a patch....
>> I've read it and not come up with an answer due to some other issues at
>> hand. E1000 hardware works differently and this has been asked before, but
>> the cards itself are in low power state when down. Changing this to bring
>> up the link would make the card start to consume lots more power, which
>> would automatically suck enormously for anyone using a laptop.
>>
>> Unfortunately, we have no way to distinguish directly between mobile and
>> non-mobile adapters, since they are usually the same.
>>
>> Your application should really `ifconfig up` the device before checking for
>> link.
> Actually pushing the link up in userspace doesn't specifically help my
> applications, as I care about actual link status (as reported by
> ethtool).
technically the link is already up if the cable is inserted and connected. doing an
`ifconfig up` doesn't change that. If the link is down then this powers up the PHY so we
can read the link status.
> Is there no way to keep the link status correct (within 0.5 seconds),
> without bringing the card to full power? Maybe a timer that fires a
> proper check (with the power implications).
no, not that I know of.
> Would a patch that adds a modparam (not enabled by default) running the
> behavior I'm after, be acceptable, so the e1000 driver can act identical
> to all of the other drivers?
I bet that all drivers work fine if you `ifconfig up` them. What happens if other NIC
drivers implement similar powersaving methods and start working the same?
Cheers,
Auke
next prev parent reply other threads:[~2006-11-07 22:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-06 1:31 e1000/ICH8LAN weirdness - no ethtool link until initially forced up Robin H. Johnson
2006-11-07 7:14 ` Pavel Machek
2006-11-07 15:51 ` Auke Kok
2006-11-07 19:35 ` Theodore Tso
2006-11-08 15:59 ` Auke Kok
2006-11-07 21:31 ` Robin H. Johnson
2006-11-07 22:32 ` Auke Kok [this message]
2006-11-08 3:56 ` Robin H. Johnson
2006-11-08 12:04 ` Pavel Machek
2006-11-08 19:54 ` General network driver suspend/resume (was e1000 carrier related) Stephen Hemminger
2006-11-08 19:54 ` Stephen Hemminger
2006-11-08 21:10 ` Auke Kok
2006-11-08 21:33 ` 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=45510980.2040808@intel.com \
--to=auke-jan.h.kok@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=robbat2@gentoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.