From: Kalle Valo <kalle.valo@iki.fi>
To: Christian Lamparter <chunkeey@googlemail.com>
Cc: Jan Kiszka <jan.kiszka@web.de>, linux-wireless@vger.kernel.org
Subject: Re: [RFT] ar9170: AP broadcast buffering
Date: Tue, 08 Dec 2009 09:23:39 +0200 [thread overview]
Message-ID: <871vj63p50.fsf@purkki.valot.fi> (raw)
In-Reply-To: <200912072231.32798.chunkeey@googlemail.com> (Christian Lamparter's message of "Mon\, 7 Dec 2009 22\:31\:32 +0100")
Christian Lamparter <chunkeey@googlemail.com> writes:
> On Monday 07 December 2009 21:08:32 Kalle Valo wrote:
>
>> I don't know what time constraints you refer to here, but clients
>> should stay awake until they have received a multicast/broadcast
>> message with the moredata bit disabled. So, in theory, it doesn't
>> matter even if the frames are transmitted even 20 ms after the beacon.
>> (In practise some hardware might have timers for this, I think at
>> least wl1251 had one.)
>
>> Of course the downside is the increased power consumption. But it's
>> still better than to not receive the multicast/broadcast frames at
>> all :)
>
> That's the thing: 802.11-2007 11.2.1.5 f) says:
> "*Immediately* after every DTIM, the AP shall
> transmit all buffered broadcast/multicast MSDUs...".
> And I cannot rule out that some Devs took this quite literally. ;-)
Well, "immediately" is relative. If my wife says to immeaditely do
something, it might take a week before I'll do it ;)
> Anyway, here is a case that I've witnessed:
>
> During testing, I caught samples where MC/BC frames were delayed for
> more up to 115ms. (b_interval = 102.4ms and dtim_period = 3)
Yeah, if the time is longer than the beacon interval then it won't
definitely work.
--
Kalle Valo
next prev parent reply other threads:[~2009-12-08 7:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-29 1:06 [RFT] ar9170: AP broadcast buffering Christian Lamparter
2009-12-06 18:23 ` Jan Kiszka
2009-12-07 16:36 ` Christian Lamparter
2009-12-07 20:08 ` Kalle Valo
2009-12-07 21:31 ` Christian Lamparter
2009-12-08 7:23 ` Kalle Valo [this message]
2009-12-08 21:51 ` Jan Kiszka
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=871vj63p50.fsf@purkki.valot.fi \
--to=kalle.valo@iki.fi \
--cc=chunkeey@googlemail.com \
--cc=jan.kiszka@web.de \
--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).