From: Kalle Valo <kalle.valo@iki.fi>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Dan Williams <dcbw@redhat.com>, "Guy\,
Wey-Yi W" <wey-yi.w.guy@intel.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
Matthew Garrett <mjg@redhat.com>,
Marcel Holtmann <marcel@holtmann.org>
Subject: Re: more thoughts on power saving (was: wireless powersaving (in NM?))
Date: Wed, 01 Apr 2009 14:12:59 +0300 [thread overview]
Message-ID: <87zlf0hbk4.fsf@litku.valot.fi> (raw)
In-Reply-To: <1238583879.5970.195.camel@johannes.local> (Johannes Berg's message of "Wed\, 01 Apr 2009 13\:04\:39 +0200")
Johannes Berg <johannes@sipsolutions.net> writes:
> Hi,
>
> So I had a few more thoughts.
>
> Let me start with a story :)
>
> I use my N810 device for landline calls via SIP these days.
> Every time I'm in a call, audio is very choppy and I can barely
> understand the person I'm talking to -- my fix is to "ping -i
> 0.05" the device to disable its powersaving...
>
>
> Now, why is audio choppy? I was blaming it on the wireless powersaving,
> and disabling that clearly fixes it. But is the problem really just
> there? I think it might also be the application -- its playback buffer
> is smaller than the networking latency I am experiencing due to
> wireless. I think I could probably tolerate an additional audio latency
> of 150ms (my beacon interval being 102.4ms) or so, if audio wasn't
> choppy.
What's the DTIM count in your AP? N810 wakes up only for DTIM beacons,
that might increase the latency.
> That means the application (telepathy sofiasip I guess) would have
> to have 150ms or so playback buffer to make the playback smooth with
> delay. [1]
[...]
> [1] I don't quite see why this doesn't happen automatically, it seems it
> must discard packets that don't fit into its idea of the stream timing
N810 only disables the power save when there's a frame to transmit. I
guess the SIP connection isn't constantly sending anything and that's
why you get bad quality.
--
Kalle Valo
next prev parent reply other threads:[~2009-04-01 11:13 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 10:39 wireless powersaving (in NM?) Johannes Berg
2009-03-24 10:32 ` Marcel Holtmann
2009-03-25 10:45 ` Johannes Berg
2009-03-24 13:47 ` John W. Linville
2009-03-24 13:53 ` Johannes Berg
2009-03-24 14:47 ` Guy, Wey-Yi W
2009-03-24 15:03 ` Kalle Valo
2009-03-24 14:17 ` Kalle Valo
2009-03-25 10:57 ` Johannes Berg
2009-03-25 19:53 ` Kalle Valo
2009-03-25 20:06 ` Johannes Berg
2009-03-25 20:09 ` Johannes Berg
2009-03-25 20:22 ` Kalle Valo
2009-03-24 15:59 ` Dan Williams
2009-03-25 11:04 ` Johannes Berg
2009-03-25 15:31 ` Dan Williams
2009-03-25 15:48 ` Johannes Berg
2009-03-26 8:00 ` Luis R. Rodriguez
2009-03-26 8:11 ` Johannes Berg
2009-03-26 8:39 ` Luis R. Rodriguez
2009-03-26 8:54 ` Johannes Berg
2009-03-26 9:01 ` Luis R. Rodriguez
2009-03-26 14:29 ` Georgy Berdyshev
2009-03-26 8:19 ` Kalle Valo
2009-03-26 8:40 ` Luis R. Rodriguez
2009-03-31 16:28 ` Johannes Berg
2009-04-01 11:04 ` more thoughts on power saving (was: wireless powersaving (in NM?)) Johannes Berg
2009-04-01 11:12 ` Kalle Valo [this message]
2009-04-01 14:29 ` Guy, Wey-Yi W
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=87zlf0hbk4.fsf@litku.valot.fi \
--to=kalle.valo@iki.fi \
--cc=dcbw@redhat.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=mjg@redhat.com \
--cc=wey-yi.w.guy@intel.com \
/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.