linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Eliad Peller <eliad@wizery.com>
Cc: Kalle Valo <kvalo@adurom.com>, Luciano Coelho <coelho@ti.com>,
	linux-wireless@vger.kernel.org
Subject: Re: [PATCH] mac80211: add ieee80211_set_dyn_ps_timeout()
Date: Tue, 20 Sep 2011 14:13:50 +0200	[thread overview]
Message-ID: <1316520830.3953.19.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <CAB3XZEeMZvv374SBTPDg1W8-E24=K5yVRhDQ0ktpUgxAEJgdzw@mail.gmail.com> (sfid-20110920_140619_504198_304C20F0)

On Tue, 2011-09-20 at 15:05 +0300, Eliad Peller wrote:

> > It'd be interesting to see if we can just treat this as a "minimum awake
> > time", kinda like going back to the range I thought about earlier.
> >
> do you mean something like:
> diff --git a/net/mac80211/mlme.c b/net/mac80211/mlme.c
> index 4274e94..57695e3 100644
> --- a/net/mac80211/mlme.c
> +++ b/net/mac80211/mlme.c
> @@ -702,11 +702,12 @@ void ieee80211_recalc_ps(struct ieee80211_local
> *local, s32 latency)
>                         if (latency > (1900 * USEC_PER_MSEC) &&
>                             latency != (2000 * USEC_PER_SEC))
>                                 timeout = 0;
> -                       else if (local->dynamic_ps_driver_timeout >= 0)
> -                               timeout = local->dynamic_ps_driver_timeout;
>                         else
>                                 timeout = 100;
>                 }
> +               if (timeout && local->dynamic_ps_driver_timeout > timeout)
> +                       timeout = local->dynamic_ps_driver_timeout;
> +
>                 local->dynamic_ps_user_timeout = timeout;
>                 if (!local->disable_dynamic_ps)
>                         conf->dynamic_ps_timeout =
> 
> ?
> 
> i don't find it much different.

I did mean something like that, yes, but I was thinking we actually
calculate the timeout based on latency requirements :)

johannes


  reply	other threads:[~2011-09-20 12:13 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-18 12:03 [PATCH] mac80211: add ieee80211_set_dyn_ps_timeout() Eliad Peller
2011-09-19  5:09 ` Luciano Coelho
2011-09-19 12:05   ` Johannes Berg
2011-09-19 16:01     ` Eliad Peller
2011-09-20 12:13       ` Johannes Berg
2011-09-19 15:41   ` Kalle Valo
2011-09-19 16:30     ` Eliad Peller
2011-09-19 16:38       ` Johannes Berg
2011-09-20  8:37         ` Kalle Valo
2011-09-20  8:59           ` Ohad Ben-Cohen
2011-09-20 15:00             ` Kalle Valo
2011-09-20 12:05         ` Eliad Peller
2011-09-20 12:13           ` Johannes Berg [this message]
2011-09-20 12:28             ` Eliad Peller
2011-09-20  8:34       ` Kalle Valo
2011-09-20  8:49         ` Ohad Ben-Cohen
2011-09-20 14:49           ` Kalle Valo
2011-09-20 18:36             ` Luis R. Rodriguez
2011-09-20 22:32               ` Eliad Peller
2011-09-20 21:44             ` Ohad Ben-Cohen
2011-09-21  6:34               ` 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=1316520830.3953.19.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=coelho@ti.com \
    --cc=eliad@wizery.com \
    --cc=kvalo@adurom.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 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).