All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Florian Zumbiehl <florz@florz.de>
Cc: flamingice@sourmilk.net, andreamrl@tiscali.it,
	herton@mandriva.com.br, htl10@users.sourceforge.net,
	linux-wireless@vger.kernel.org
Subject: Re: Power consumption of RTL8187 (driver)/recommendations for	low-power USB 802.11 adapter?
Date: Fri, 18 Dec 2009 12:20:19 -0600	[thread overview]
Message-ID: <4B2BC7E3.2050907@lwfinger.net> (raw)
In-Reply-To: <20091218180205.GD2512@florz.florz.dyndns.org>

On 12/18/2009 12:02 PM, Florian Zumbiehl wrote:
> Hi,
> 
> I'm not really sure whom to write to, so ... I'm writing to all of you, for
> now ;-)
> 
> I just bought a USB wireless stick with an RTL8187B inside. The idea was to
> use it with my laptop. In principle, it works just fine ... if it didn't
> cause the computer to triple its idle power consumption from some
> 7.5 to ~ 22.5 Watts.
> 
> I don't have a clue (yet) where exactly all that power goes to, and how
> much of it is actually being used by the stick itself (it's getting pretty
> warm, too - maybe you have a clue what to expect there?). But apparently,
> quite a bit of that increased power consumption is due to the CPU entering
> ACPI sleep states for a much smaller proportion of time, and not entering
> the highest sleep state at all anymore (which otherwise makes up around
> 98 % of the time) due to some polling/high-frequency interrupt of the
> driver. After all, even the most inefficient voltage regulator can't
> make 15 W from USB's max. 2.5 W (I hope ...).

My RTL8187B does get quite warm. The 'lsusb -v' output says that the
device can draw up to 500 mA or the maximum 2.5 W, but it does seem
warmer than that.

> Now, the obvious question is: Is there anything one could do about that?

AFAIK, the rtl8187 driver is not running any polling loops. It will
interrupt the machine whenever it receives something or whenever data
needs to be transmitted. You could cut the frequency by changing the
beacon interval to 2 s. It is probably now set at 0.1 s.

> And if not, or possibly even if: Any recommendation for a power-efficient
> USB 802.11 adapter - in particular something that does not cause
> CPU wakeups all the time when there is no actual network traffic?

Not all network traffic is data.

Larry

  reply	other threads:[~2009-12-18 18:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-18 18:02 Power consumption of RTL8187 (driver)/recommendations for low-power USB 802.11 adapter? Florian Zumbiehl
2009-12-18 18:20 ` Larry Finger [this message]
2009-12-18 18:59   ` Florian Zumbiehl
2009-12-18 23:28     ` Larry Finger
2009-12-19  0:15       ` Andrea Merello
2009-12-19  1:13         ` Florian Zumbiehl
2009-12-19 10:30           ` Andrea Merello
2009-12-19 15:32             ` Hin-Tak Leung
2009-12-19 18:44             ` Florian Zumbiehl
2009-12-19 23:31               ` Hin-Tak Leung
2009-12-21 21:27                 ` Florian Zumbiehl
2009-12-20 18:43         ` Kalle Valo
2009-12-19  0:37       ` Florian Zumbiehl
2009-12-19 10:19         ` Andrea Merello

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=4B2BC7E3.2050907@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=andreamrl@tiscali.it \
    --cc=flamingice@sourmilk.net \
    --cc=florz@florz.de \
    --cc=herton@mandriva.com.br \
    --cc=htl10@users.sourceforge.net \
    --cc=linux-wireless@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.