From: Auke Kok <auke-jan.h.kok@intel.com>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: stern@rowland.harvard.edu, netdev@vger.kernel.org, david-b@pacbell.net
Subject: Re: Runtime power management for network interfaces
Date: Mon, 31 Jul 2006 09:19:18 -0700 [thread overview]
Message-ID: <44CE2D86.3040800@intel.com> (raw)
In-Reply-To: <20060730200631.836bdd23.rdunlap@xenotime.net>
Randy.Dunlap wrote:
> On Tue, 25 Jul 2006 09:20:06 -0700 Auke Kok wrote:
>
>> Alan Stern wrote:
>>> During a Power Management session at the Ottawa Linux Symposium, it was
>>> generally agreed that network interface drivers ought to automatically
>>> suspend their devices (if possible) whenever:
>>>
>>> (1) The interface is ifconfig'ed down, or
>>>
>>> (2) No link is available.
>>>
>>> Presumably (1) should be easy enough to implement. (2) might or might not
>>> be feasible, depending on how much WOL support is available. (It might
>>> not be feasible at all for wireless networking.) Still, there can be no
>>> question that it would be a Good Thing for laptops to power-down their
>>> ethernet controllers when the network cable is unplugged.
>>>
>>> Has any progress been made in this direction? If not, a natural approach
>>> would be to start with a reference implementation in one driver which
>>> could then be copied to other drivers.
>>
>> Intel's newer e1000's (ich7 onboard e1000 and newer versions for instance)
>> already support this feature partially - the MAC stays on but the PHY can be
>> powered off when no link is present.
>>
>> In order to enable this feature you will need to turn it on explicitly at load
>> time:
>>
>> modprobe e1000 SmartPowerDownEnable=1
>
> Please add that to Documentation/networking/e1000.txt.
I'm long overdue with documentation updates ATM, I'll see if I can fix that :)
Cheers,
Auke
next prev parent reply other threads:[~2006-07-31 16:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-25 15:59 Runtime power management for network interfaces Alan Stern
2006-07-25 16:20 ` Auke Kok
2006-07-31 3:06 ` Randy.Dunlap
2006-07-31 16:19 ` Auke Kok [this message]
2006-07-25 17:03 ` David Brownell
2006-07-31 16:17 ` Stephen Hemminger
2006-08-01 0:29 ` David Brownell
2006-08-01 15:53 ` Stephen Hemminger
2006-08-01 15:18 ` Lennert Buytenhek
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=44CE2D86.3040800@intel.com \
--to=auke-jan.h.kok@intel.com \
--cc=david-b@pacbell.net \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=stern@rowland.harvard.edu \
/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).