netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* WLAN power saving: brain dump
@ 2004-11-16 14:30 Werner Almesberger
  2004-11-21 19:22 ` Harald Welte
  0 siblings, 1 reply; 3+ messages in thread
From: Werner Almesberger @ 2004-11-16 14:30 UTC (permalink / raw)
  To: netdev

This is just a brain dump, so that the ideas are out in public.
Some day, I might actually implement this, unless somebody else
beats me to it :-)

These reflections are my own. I made them while reading 
specifications of WLAN cards with growing horror.

Looking at WLAN cards, they uniformly seem to have excessive
power consumption even if just laying in wait. This is
particularly annoying for devices with otherwise very low
power consumption, such as PDAs.

It would seem to me that the typical use of such a device would
allow for completely powering down the WLAN card if not needed.
In particular, all packets reaching a normal PDA are in response
to some previous and comparably recent emission from that device.

Furthermore, we generally have a fairly good idea of when we
still want to send something, and, although to a lesser extent,
when we're expecting incoming data.

So actively powering down a WLAN card while idle could use the
following inputs:

- an indication of whether any socket has a non-empty send queue
- the time since the last time all send queues were empty (we want
  to have a certain cool-off period, for various reasons, including
  connectionless activity like ARP or UDP)
- an indication if whether any sockets have a read or a poll or
  select for reading pending (this is very unreliable, but may
  provide useful input with some appliations)
- time since the last successful reception
- an indication of whether any sockets have pending out-of-order
  data
- a manual override

All this should be keyed by interface. Things to consider:

- the time and power it takes to bring a WLAN card back online
- the time we regularly have to wait for something to happen
  even if we seem to be able, e.g. the delay between sending an
  HTTP GET and a response (if we can get hints from the Web
  client, no guessing is needed here)
- the correlation between idle time and future idleness from the
  user

There's probably more. For a proof of concept implementation, it
should be sufficient to consider ARP, DNS, SSH/SCP, and HTTP(S).

- Werner

-- 
  _________________________________________________________________________
 / Werner Almesberger, Buenos Aires, Argentina         wa@almesberger.net /
/_http://www.almesberger.net/____________________________________________/

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2004-11-22  0:44 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-11-16 14:30 WLAN power saving: brain dump Werner Almesberger
2004-11-21 19:22 ` Harald Welte
2004-11-22  0:44   ` Werner Almesberger

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).