From: Kalle Valo <kvalo@adurom.com>
To: Juuso Oikarinen <juuso.oikarinen@nokia.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFC PATCHv2 1/2] mac80211: Determine dynamic PS timeout based on ps-qos network latency
Date: Fri, 16 Apr 2010 08:17:57 +0300 [thread overview]
Message-ID: <87eiigm0vu.fsf@purkki.valot.fi> (raw)
In-Reply-To: <1271228079-27321-2-git-send-email-juuso.oikarinen@nokia.com> (Juuso Oikarinen's message of "Wed\, 14 Apr 2010 09\:54\:38 +0300")
Juuso Oikarinen <juuso.oikarinen@nokia.com> writes:
> Determine the dynamic PS timeout based on the configured ps-qos network
> latency. For backwards wext compatibility, allow the dynamic PS timeout
> configured by the cfg80211 to overrule the automatically determined value.
Thanks. I took a quick look, but I haven't tested this yet myself.
> + timeout = local->hw.conf.dynamic_ps_forced_timeout;
> + if (timeout < 0) {
> + if (latency <= 50000)
> + timeout = 300;
> + else if (latency <= 2000000000)
> + timeout = 100;
> + else
> + timeout = 0;
> + }
> + local->hw.conf.dynamic_ps_timeout = timeout;
What will be the timeout value when there are no pm_qos requirements
from user space applications? Do you know what will be the default
latency value in that case?
I'm mostly worried about timeout 0 case, for example I suspect ath9k
is broken with that value.
Also does this patch change the default value of dynamic ps timeout?
--
Kalle Valo
next prev parent reply other threads:[~2010-04-16 5:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-14 6:54 [RFC PATCHv2 0/2] mac80211: cfg80211: dynamic ps timeout based on pm-qos Juuso Oikarinen
2010-04-14 6:54 ` [RFC PATCHv2 1/2] mac80211: Determine dynamic PS timeout based on ps-qos network latency Juuso Oikarinen
2010-04-16 5:17 ` Kalle Valo [this message]
2010-04-16 5:29 ` Juuso Oikarinen
2010-04-16 6:10 ` Kalle Valo
2010-04-16 6:17 ` Juuso Oikarinen
2010-04-14 6:54 ` [RFC PATCHv2 2/2] cfg80211: Remove default dynamic PS timeout value Juuso Oikarinen
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=87eiigm0vu.fsf@purkki.valot.fi \
--to=kvalo@adurom.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 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).