public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Kok, Auke" <auke-jan.h.kok@intel.com>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: 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: Tue, 09 Oct 2007 11:41:17 -0700	[thread overview]
Message-ID: <470BCB4D.8090307@intel.com> (raw)
In-Reply-To: <20071009182857.GF4003@csclub.uwaterloo.ca>

Lennart Sorensen wrote:
> On Mon, Oct 08, 2007 at 03:31:51PM -0700, Kok, Auke wrote:
>> you most certainly want to do this in userspace I think.
>>
>> One of the biggest problems is that link negotiation can take a significant amount
>> of time, well over several seconds (1 to 3 seconds typical) with gigabit, and
>> having your ethernet connection go offline for 3 seconds may not be the desired
>> effect for when you want to get more bandwidth in the first place.
>>
>> However, when a laptop is in battery mode, switching down from gigabit to 100mbit
>> makes a lot more sense, so this is something I would recommend. This can be as
>> easy as changing the advertisement mask of the interface and renegotiating the
>> link. Userspace could handle that very easily.
> 
> Now if you were trying to transfer a lot of data to the laptop, would it
> be more power efficient to do it at gigabit speeds so you can finish
> sooner and shut down the machine entirely, or to slow to 100mbit and
> take longer to do it, and hence spend more time powering the cpu and
> ram?

my suspicion is that the cost of switching is much higher than what you would
consume running at 100mbit, even if the amount of data is quite large. going
offline to renegotiate the link would already cost you 3W typically.

I definately think that userspace is the right field to solve this problem: let
the users decide how to use the available power on their sytems through a decent
power profile tool (perhaps gnome-power-manager or something like that). This way
the user can choose.

Auke

  reply	other threads:[~2007-10-09 18:41 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-08 22:07 gigabit ethernet power consumption 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 [this message]
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
     [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           ` Bodo Eggert
2007-10-12 16:35             ` Kok, Auke
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

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=470BCB4D.8090307@intel.com \
    --to=auke-jan.h.kok@intel.com \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lsorense@csclub.uwaterloo.ca \
    --cc=pavel@ucw.cz \
    /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