From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <mcgrof@frijolero.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [RFC 04/15] mac80211: split PS buffers into ACs
Date: Wed, 28 Sep 2011 09:10:55 +0200 [thread overview]
Message-ID: <1317193855.3986.4.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <CAB=NE6Wi1EJtyW=4kCNTgdhjzzgTMT3N7xhgKu+AWd9cphcD5Q@mail.gmail.com> (sfid-20110927_225152_449291_118F1AA2)
On Tue, 2011-09-27 at 13:51 -0700, Luis R. Rodriguez wrote:
> > + /*
> > + * If all ACs are delivery-enabled then we should build
> > + * the TIM bit for all ACs anyway; if only some are then
> > + * we ignore those and build the TIM bit using only the
> > + * non-enabled ones.
> > + */
>
> As per the documentation uapsd_queues is the "bitmap of queues
> configured for uapsd". As I read this we are ignoring setting the TIM
> for the STA if an AC queue was marked as uapsd-enabled but had
> buffered frames for it, so we'd only set the TIM if we had at least
> one AC queue that did not have uapsd enabled and had buffered frames
> pending. Is that accurate?
Almost.
First of all, we need to differentiate between delivery- and
trigger-enabled, which currently we don't. Since this only happens with
TSPEC, we're not worried about that right now, but it's good to keep it
in mind. So right now, the uapsd_queues bitmap marks those that are both
trigger- and delivery-enabled.
Now, to the TIM bit: when *all* ACs are delivery-enabled, the TIM bit
will be set from all ACs. This is the case you missed. When only some of
the ACs are delivery-enabled, the delivery-enabled ACs are ignored for
purposes of setting the TIM bit. This is what you described.
This is described in 11.2.1.5 (IIRC).
johannes
next prev parent reply other threads:[~2011-09-28 7:10 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 15:47 [RFC 00/15] mac80211 uAPSD support Johannes Berg
2011-09-22 15:47 ` [RFC 01/15] mac80211: let drivers inform it about per TID buffered frames Johannes Berg
2011-09-22 15:47 ` [RFC 02/15] mac80211: unify TIM bit handling Johannes Berg
2011-09-22 15:47 ` [RFC 03/15] mac80211: also expire filtered frames Johannes Berg
2011-09-26 22:30 ` Luis R. Rodriguez
2011-09-27 2:26 ` Adrian Chadd
2011-09-27 7:50 ` Johannes Berg
2011-09-27 12:24 ` Adrian Chadd
2011-09-27 12:25 ` Adrian Chadd
2011-09-27 7:47 ` Johannes Berg
2011-09-22 15:47 ` [RFC 04/15] mac80211: split PS buffers into ACs Johannes Berg
2011-09-27 20:51 ` Luis R. Rodriguez
2011-09-28 7:10 ` Johannes Berg [this message]
2011-09-22 15:47 ` [RFC 05/15] mac80211: remove return value from add_pending_skbs Johannes Berg
2011-09-22 15:47 ` [RFC 06/15] mac80211: clear more-data bit on filtered frames Johannes Berg
2011-09-22 15:47 ` [RFC 07/15] mac80211: allow releasing driver-buffered frames Johannes Berg
2011-09-22 15:47 ` [RFC 08/15] mac80211: implement uAPSD Johannes Berg
2011-09-22 15:47 ` [RFC 09/15] mac80211: send (QoS) Null if no buffered frames Johannes Berg
2011-09-22 15:47 ` [RFC 10/15] mac80211: reply only once to each PS-poll Johannes Berg
2011-09-22 15:47 ` [RFC 11/15] mac80211: optimise station flags Johannes Berg
2011-09-22 15:47 ` [RFC 12/15] mac80211: add missing station flags to debugfs Johannes Berg
2011-09-22 15:47 ` [RFC 13/15] mac80211: explicitly notify drivers of frame release Johannes Berg
2011-09-22 15:47 ` [RFC 14/15] mac80211: allow out-of-band EOSP notification Johannes Berg
2011-09-22 15:47 ` [RFC 15/15] mac80211: document client powersave Johannes Berg
2011-09-22 15:52 ` [RFC 00/15] mac80211 uAPSD support Johannes Berg
2011-09-22 23:25 ` Luis R. Rodriguez
2011-09-23 8:59 ` Johannes Berg
2011-09-23 18:06 ` Dmitry Tarnyagin
2011-09-23 18:14 ` Johannes Berg
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=1317193855.3986.4.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@frijolero.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).