From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <lrodriguez@atheros.com>
Cc: Jouni Malinen <j@w1.fi>,
linux-wireless@vger.kernel.org, Kalle Valo <kvalo@adurom.com>,
Amod Bodas <Amod.Bodas@atheros.com>
Subject: Re: [RFT] mac80211: fix broadcast/multicast data drop on scan
Date: Fri, 27 Aug 2010 17:58:42 +0200 [thread overview]
Message-ID: <1282924722.4377.17.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <AANLkTikkemr390C4N2bPivp9rZhbdSpUw9=+uvS=y-Mq@mail.gmail.com>
On Fri, 2010-08-27 at 08:55 -0700, Luis R. Rodriguez wrote:
> On Fri, Aug 27, 2010 at 8:51 AM, Johannes Berg
> <johannes@sipsolutions.net> wrote:
> > On Fri, 2010-08-27 at 08:48 -0700, Luis R. Rodriguez wrote:
> >
> >> > Well, there's no way we can reliably wake up exactly before a beacon by
> >> > implementing that in software, hard real-time hasn't been achieved in
> >> > Linux yet :-)
> >>
> >> Keyword here is *exactly*. I don't want to wake up *exactly* at DTIM,
> >> only ensure we don't sleep during it and the send buffered frames and
> >> multicast traffic data. Why can we not implement this on mac80211?
> >
> > Well, how long before the beacon do you want to wake up to catch it?
> > 1ms? 10ms? 100ms? 1000ms? What if the system is busy?
>
> I cannot say what would work best, how about half a beacon interval early?
Why are we even discussing this anyway? It doesn't matter for a power
save implementation since you better offload it to the device so you get
as exact timing as you can?
johannes
next prev parent reply other threads:[~2010-08-27 15:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-27 5:38 [RFT] mac80211: fix broadcast/multicast data drop on scan Luis R. Rodriguez
2010-08-27 9:06 ` Jouni Malinen
2010-08-27 15:28 ` Luis R. Rodriguez
2010-08-27 15:37 ` Johannes Berg
2010-08-27 15:40 ` Luis R. Rodriguez
2010-08-27 15:43 ` Johannes Berg
2010-08-27 15:48 ` Luis R. Rodriguez
2010-08-27 15:51 ` Johannes Berg
2010-08-27 15:55 ` Luis R. Rodriguez
2010-08-27 15:58 ` Johannes Berg [this message]
2010-08-27 18:30 ` Luis R. Rodriguez
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=1282924722.4377.17.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=Amod.Bodas@atheros.com \
--cc=j@w1.fi \
--cc=kvalo@adurom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=lrodriguez@atheros.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 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).