From: Johannes Berg <johannes@sipsolutions.net>
To: Janusz Dziedzic <janusz.dziedzic@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: mac80211: UAPSD - first release HW buffered frames next also check mac80211 buffered frames
Date: Fri, 04 Nov 2011 16:07:06 +0100 [thread overview]
Message-ID: <1320419226.3969.94.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <CAFED-jnG8+4U49scyEu8Yd7=WXFKGcrqcWw1EtTtaiVsQpwcdQ@mail.gmail.com> (sfid-20111104_160506_868196_9C6CE817)
On Fri, 2011-11-04 at 16:04 +0100, Janusz Dziedzic wrote:
> Hello,
>
> Seems currently we have implementation.
>
> if(!driver_release_tids) {
> ...
> } else {
> ...
> }
>
> Shouldn't we first release HW buffered frames and next check also SW
> buffered frames?
Only one of them can be true -- we don't release from driver & mac80211
queues at the same time. Technically we could, but the complexity would
be much higher than your simple patch for more-data handling etc.
johannes
prev parent reply other threads:[~2011-11-04 15:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-04 15:04 mac80211: UAPSD - first release HW buffered frames next also check mac80211 buffered frames Janusz Dziedzic
2011-11-04 15:07 ` Johannes Berg [this message]
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=1320419226.3969.94.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=janusz.dziedzic@gmail.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