From: Johannes Berg <johannes@sipsolutions.net>
To: Marco Porsch <marco.porsch@etit.tu-chemnitz.de>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [mac80211] UAPSD: WLAN_STA_PS flag cleared prematurely?
Date: Fri, 16 Mar 2012 13:44:12 +0100 [thread overview]
Message-ID: <1331901852.6753.2.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <4F630757.6070901@etit.tu-chemnitz.de>
On Fri, 2012-03-16 at 10:26 +0100, Marco Porsch wrote:
> Hi all,
>
> in sta_info.c : ieee80211_sta_ps_deliver_response the
> IEEE80211_TX_STATUS_EOSP is set for all to-be-sent frames, not only for
> the last. But only the last buffered frame actually gets the EOSP flag.
>
>
> /* set EOSP for the frame */
> if (reason == IEEE80211_FRAME_RELEASE_UAPSD &&
> qoshdr && skb_queue_empty(&frames))
> *qoshdr |= IEEE80211_QOS_CTL_EOSP;
>
> info->flags |= IEEE80211_TX_STATUS_EOSP |
> IEEE80211_TX_CTL_REQ_TX_STATUS;
>
>
> Consequence is, that the WLAN_STA_SP flag gets cleared (multiple times)
> in ieee80211_tx_status before the last frame with EOSP has been sent.
> Is this correct?
Looks like the bug is above, the EOSP/TX_STATUS should only be set for
the last frame?
johannes
next prev parent reply other threads:[~2012-03-16 12:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 9:26 [mac80211] UAPSD: WLAN_STA_PS flag cleared prematurely? Marco Porsch
2012-03-16 12:44 ` Johannes Berg [this message]
2012-03-16 13:38 ` Marco Porsch
2012-03-16 13:40 ` Johannes Berg
2012-03-16 13:58 ` Marco Porsch
2012-03-16 14:30 ` [PATCH] mac80211: end service period only after sending last buffered frame Marco Porsch
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=1331901852.6753.2.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=marco.porsch@etit.tu-chemnitz.de \
/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).