linux-kernel - Re: gigabit ethernet power consumption

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <47163A95.1000708@intel.com>
Date:	Wed, 17 Oct 2007 09:38:45 -0700
From:	"Kok, Auke" <auke-jan.h.kok@...el.com>
To:	Lennart Sorensen <lsorense@...lub.uwaterloo.ca>
CC:	Valdis.Kletnieks@...edu, 7eggert@....de, prasad@...ux.vnet.ibm.com,
	Pavel Machek <pavel@....cz>,
	Arjan van de Ven <arjan@...radead.org>,
	kernel list <linux-kernel@...r.kernel.org>
Subject: Re: gigabit ethernet power consumption

Lennart Sorensen wrote:
> On Fri, Oct 12, 2007 at 01:46:33PM -0700, Kok, Auke wrote:
>> I would assume that that is true for all PHY's - if there is no link to keep the
>> carrier active on I would think that the power consumption is nominal across the
>> board. Once the PHY detects link pulses it should obviously use different power
>> levels to negotiate the link for each speed.
>>
>> PHY autonegotiation just works the same across the board - the PHY's send out
>> little pulses (iow nominal power consumption) to detect a link partner, and only
>> when one is found do they engage in more aggressive conversation to establish
>> capabilities across the link.
> 
> Too bad not much can be done about fibre ports, but then again you can't
> even change speeds on those.  Then again those are not on laptops or
> other low power devices in the first place.

the only thing we do for fiber ports is power off the laser if the user explicitly
powers them down at shutdown. Note that WoL needs to be disabled for that.

Auke
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/