All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Juuso Oikarinen <juuso.oikarinen@nokia.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"Ylälehto Janne Jouko" <janne.ylalehto@nokia.com>
Subject: Re: [RFC PATCH] nl80211: Add support for dynamic ps timeout configuration
Date: Mon, 12 Apr 2010 11:06:15 +0200	[thread overview]
Message-ID: <1271063175.3877.13.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1271062589.10120.1169.camel@wimaxnb.nmp.nokia.com>

On Mon, 2010-04-12 at 11:56 +0300, Juuso Oikarinen wrote:

> We could obviously do that. This patch does not prevent adding
> functionality ;)

Well yeah but why let userspace make arbitrary decisions? :)

> For desktops, obviously reduced latency is desirable, while increased
> power consumption is not so much of an issue. For hand-held devices the
> situation is often the opposite: in many situations we might want to
> sacrifice some latency just to stretch the battery life that last inch
> longer, possibly depending on the type of traffic we know we have going
> on.

I don't think this contradicts each other. And we can also factor in the
network_latency pm_qos value. Keep in mind that the gain from the
timeout goes down as it increases past the beacon interval.

In some sense I think it would be smarter to implement a gradual
powersave policy where the device first still wakes up for every beacon
and only later goes down to waking up for DTIM only (which may or may
not be the same ...)

johannes


  reply	other threads:[~2010-04-12  9:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-12  8:11 [RFC PATCH] nl80211: Add support for dynamic ps timeout configuration Juuso Oikarinen
2010-04-12  8:32 ` Johannes Berg
2010-04-12  8:56   ` Juuso Oikarinen
2010-04-12  9:06     ` Johannes Berg [this message]
2010-04-12  9:45       ` Juuso Oikarinen
2010-04-12 20:57         ` Kalle Valo
2010-04-13  5:16           ` Juuso Oikarinen
2010-04-13  7:29           ` Juuso Oikarinen
2010-04-13  8:31             ` Kalle Valo
2010-04-13  8:49               ` Juuso Oikarinen
2010-04-13  9:07                 ` Kalle Valo
2010-04-13  9:10                   ` Juuso Oikarinen
2010-04-13 11:00                     ` Kalle Valo
2010-04-13 19:28                     ` Luis R. Rodriguez
2010-04-12 20:19   ` Kalle Valo

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=1271063175.3877.13.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=janne.ylalehto@nokia.com \
    --cc=juuso.oikarinen@nokia.com \
    --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.