From: "Kok, Auke" <auke-jan.h.kok@intel.com>
To: Valdis.Kletnieks@vt.edu
Cc: 7eggert@gmx.de, prasad@linux.vnet.ibm.com,
Lennart Sorensen <lsorense@csclub.uwaterloo.ca>,
Pavel Machek <pavel@ucw.cz>,
Arjan van de Ven <arjan@infradead.org>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: gigabit ethernet power consumption
Date: Fri, 12 Oct 2007 13:46:33 -0700 [thread overview]
Message-ID: <470FDD29.9030708@intel.com> (raw)
In-Reply-To: <12419.1192221016@turing-police.cc.vt.edu>
Valdis.Kletnieks@vt.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
next prev parent reply other threads:[~2007-10-12 20:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9c8XH-7gs-13@gated-at.bofh.it>
[not found] ` <9c9qN-7Rn-19@gated-at.bofh.it>
[not found] ` <9cs0n-3Dc-9@gated-at.bofh.it>
[not found] ` <9csjH-43E-33@gated-at.bofh.it>
[not found] ` <9d4yC-5hT-7@gated-at.bofh.it>
[not found] ` <9d7ZJ-2mI-11@gated-at.bofh.it>
2007-10-12 2:08 ` gigabit ethernet power consumption Bodo Eggert
2007-10-12 16:35 ` Kok, Auke
2007-10-12 20:30 ` Valdis.Kletnieks
2007-10-12 20:46 ` Kok, Auke [this message]
2007-10-17 13:00 ` Lennart Sorensen
2007-10-17 16:38 ` Kok, Auke
2007-10-08 22:07 Pavel Machek
2007-10-08 22:31 ` Kok, Auke
2007-10-09 5:18 ` Willy Tarreau
2007-10-09 18:28 ` Lennart Sorensen
2007-10-09 18:41 ` Kok, Auke
2007-10-10 20:44 ` Mark Gross
2007-10-11 15:33 ` Kok, Auke
2007-10-11 11:35 ` K.Prasad
2007-10-11 15:18 ` Kok, Auke
2007-10-10 6:35 ` Oliver Neukum
2007-10-09 5:08 ` Chris Snook
2007-10-09 6:58 ` Oliver Neukum
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=470FDD29.9030708@intel.com \
--to=auke-jan.h.kok@intel.com \
--cc=7eggert@gmx.de \
--cc=Valdis.Kletnieks@vt.edu \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
--cc=pavel@ucw.cz \
--cc=prasad@linux.vnet.ibm.com \
/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