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] [thread-next>] [day] [month] [year] [list]
Message-ID: <470FDD29.9030708@intel.com>
Date:	Fri, 12 Oct 2007 13:46:33 -0700
From:	"Kok, Auke" <auke-jan.h.kok@...el.com>
To:	Valdis.Kletnieks@...edu
CC:	7eggert@....de, prasad@...ux.vnet.ibm.com,
	Lennart Sorensen <lsorense@...lub.uwaterloo.ca>,
	Pavel Machek <pavel@....cz>,
	Arjan van de Ven <arjan@...radead.org>,
	kernel list <linux-kernel@...r.kernel.org>
Subject: Re: gigabit ethernet power consumption

Valdis.Kletnieks@...edu wrote:
> On Fri, 12 Oct 2007 09:35:15 PDT, "Kok, Auke" said:
> 
>>> How much power does a non-connected NIC consume, and can you save power
>>> by forcing 10 MBit until a link is detected (doubling negotiation time)?
>> no, the PHY consumes a minimal amount of energy when not connected, regardless of
>> whether it is advertising 10, 100 or 1000mbit.
> 
> Is that true for essentially all the chipsets we support (or at least "the vast
> majority of the ones currently found in common machines")?

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.


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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ