public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Kok, Auke" <auke-jan.h.kok@intel.com>
To: 7eggert@gmx.de
Cc: Kok@imap.glb.intel.com, 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 09:35:15 -0700	[thread overview]
Message-ID: <470FA243.6030908@intel.com> (raw)
In-Reply-To: <E1Ig9wz-0000sg-Ep@be1.lrz>

Bodo Eggert wrote:
> Kok, Auke <auke-jan.h.kok@intel.com> wrote:
>> K.Prasad wrote:
> 
>>> Without the side-effect of experiencing a link-flap when switching to a
>>> lower-speed (with its toll in terms of down-time for auto-negotiation,
>>> STP, etc), the Interrupt Moderation Algorithm dynamically adjusts the
>>> number of interrupts based on traffic - and presumably consume less
>>> power. For an "Optimise for Power" kind of profile - the driver can be
>>> loaded with a higher throttle rate during boot-time.
>> We're changing this to be run-time adjustable in newer drivers.
>>
>> However, the power consumed by your nic staying in gigabit mode is much
>> greater in the long run then what you can save by trying to scrounge for
>> milliwatts reducing interrupts generated by the nic. By default it already
>> moderates them somewhat. Practically this feature is really not useful for
>> powersaving, it just won't add up to actual benefits in a real life situtation
>> I think.
> 
> Just a thought:
> 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.

Cheers,

Auke

  reply	other threads:[~2007-10-12 16:38 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 [this message]
2007-10-12 20:30               ` Valdis.Kletnieks
2007-10-12 20:46                 ` Kok, Auke
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=470FA243.6030908@intel.com \
    --to=auke-jan.h.kok@intel.com \
    --cc=7eggert@gmx.de \
    --cc=Kok@imap.glb.intel.com \
    --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