From: Ali MJ Al-Nasrawy <alimjalnasrawy@gmail.com>
To: Arend van Spriel <arend.vanspriel@broadcom.com>
Cc: linux-wireless@vger.kernel.org,
brcm80211-dev-list.pdl@broadcom.com,
brcm80211-dev-list@cypress.com
Subject: Re: [PATCH] brcmsmac: ap mode: update beacon when TIM changes
Date: Sat, 22 Sep 2018 16:17:26 +0300 [thread overview]
Message-ID: <20180922161726.1711e766@manjaro> (raw)
In-Reply-To: <6feec186-5137-8827-8ade-6f8988144f78@broadcom.com>
On Sat, 22 Sep 2018 11:07:36 +0200
Arend van Spriel <arend.vanspriel@broadcom.com> wrote:
> On 9/11/2018 7:26 PM, Ali MJ Al-Nasrawy wrote:
> > Beacons+TIM are created/updated for fw beaconing only when
> > BSS_CHANGED_BEACON. This is not compliant with power-saving
> > stations. Fix it by updating beacon templates on mac80211 set_tim
> > callback. Adresses the issue in:
> > https://marc.info/?i=20180911163534.21312d08%20()%20manjaro
>
> A few remarks below but here is my ....
>
> Reviewed-by: Arend van Spriel <arend.vanspriel@broadcom.com>
Thank you for your review and I shall submit a second version fixing
the issues below...
> > +static int brcms_ops_beacon_set_tim(struct ieee80211_hw *hw,
> > + struct ieee80211_sta *sta, bool
> > set) +{
> > + /*FIXME: this may be more efficiently handled by delegating
> > + beacon upload to the beacon interrupt handler*/
>
> No sure what you mean by this remark. The code below looks ok to me,
> ie. same as with bss update. So please drop the remark.
TIM is updated much more frequently than bss updates and scales with
number of client stations and a simple test shows that it takes ~120us
to update the beacon templates on Core i3! So I think it may be more
efficient to split set_tim handler to a fast bottom half that just
schedules an interrupt for the next beacon and delegates the beacon
upload to the interrupt handler so that beacon templates are not
updated several times per beacon interval.
But I agree that this should neither be part of the code nor titled
FIXME-I might have exaggerated a little bit ;)
> > a/drivers/net/wireless/broadcom/brcm80211/brcmsmac/main.h +++
> > b/drivers/net/wireless/broadcom/brcm80211/brcmsmac/main.h @@ -568,6
> > +568,8 @@ struct brcms_c_info { u16 beacon_tim_offset; u16
> > beacon_dtim_period; struct sk_buff *probe_resp;
> > +
>
> Just get rid of the empty line (+TAB) above. I am not keen on storing
> the vif, but it seems there is no other way to get that.
Okay.
next prev parent reply other threads:[~2018-09-22 19:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 17:26 [PATCH] brcmsmac: ap mode: update beacon when TIM changes Ali MJ Al-Nasrawy
2018-09-20 12:04 ` Kalle Valo
2018-09-22 9:07 ` Arend van Spriel
2018-09-22 13:17 ` Ali MJ Al-Nasrawy [this message]
2018-09-22 13:41 ` [PATCH v2] brcmsmac: AP " Ali MJ Al-Nasrawy
2018-09-23 9:54 ` [PATCH v3] " Ali MJ Al-Nasrawy
2018-09-24 8:15 ` Arend van Spriel
2018-09-24 10:24 ` Ali MJ Al-Nasrawy
2018-09-26 9:04 ` Ali MJ Al-Nasrawy
2018-10-03 16:21 ` [PATCH v4] " Ali MJ Al-Nasrawy
2018-10-13 17:01 ` Kalle Valo
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=20180922161726.1711e766@manjaro \
--to=alimjalnasrawy@gmail.com \
--cc=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=brcm80211-dev-list@cypress.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).