linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: ext-saravanan.dhanabal@nokia.com, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] mac80211: Reschedule dynamic power save timer after wakeup
Date: Mon, 29 Mar 2010 13:55:06 -0400	[thread overview]
Message-ID: <20100329175506.GE4984@tuxdriver.com> (raw)
In-Reply-To: <1268841668.5989.3.camel@jlt3.sipsolutions.net>

On Wed, Mar 17, 2010 at 09:01:08AM -0700, Johannes Berg wrote:
> On Wed, 2010-03-17 at 12:09 +0100, ext-saravanan.dhanabal@nokia.com
> wrote:
> > In worst case it takes up to that much,  though the average is less but still significant. 
> 
> > On Tue, 2010-03-16 at 11:31 -0400, Saravanan Dhanabal wrote:
> > > After last transmission, the device goes to sleep earlier
> > > than the configured dynamic power save timeout. If timeout
> > > is set to 400ms, device enters into sleep mode at around
> > > 330ms since from last TX.
> 
> I still don't think I understand this patch. Why would you be interested
> in the exact timing rather than the time since the transmission? I
> mean ... why does it go to sleep _earlier_?

Any further comments on this one?

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

  reply	other threads:[~2010-03-29 18:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-16 15:31 [PATCH] mac80211: Reschedule dynamic power save timer after wakeup Saravanan Dhanabal
2010-03-16 21:42 ` Johannes Berg
2010-03-17 11:09   ` ext-saravanan.dhanabal
2010-03-17 16:01     ` Johannes Berg
2010-03-29 17:55       ` John W. Linville [this message]
2010-03-29 21:15         ` ext-saravanan.dhanabal
2010-03-30  5:33           ` Johannes Berg
2010-03-30 11:48             ` ext-saravanan.dhanabal
  -- strict thread matches above, loose matches on Subject: below --
2010-03-16 16:46 Saravanan Dhanabal

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=20100329175506.GE4984@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=ext-saravanan.dhanabal@nokia.com \
    --cc=johannes@sipsolutions.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 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).