From: Marco Porsch <marco.porsch@etit.tu-chemnitz.de>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [mac80211] UAPSD: WLAN_STA_PS flag cleared prematurely?
Date: Fri, 16 Mar 2012 14:58:22 +0100 [thread overview]
Message-ID: <4F6346FE.4060005@etit.tu-chemnitz.de> (raw)
In-Reply-To: <1331905240.6753.14.camel@jlt3.sipsolutions.net>
[-- Attachment #1.1: Type: text/plain, Size: 2248 bytes --]
On 03/16/12 14:40, Johannes Berg wrote:
> On Fri, 2012-03-16 at 14:38 +0100, Marco Porsch wrote:
>> On 03/16/12 13:44, Johannes Berg wrote:
>>> 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?
>>
>> I Agree. But what about the case, when the last frame is not a QoS
>> frame? Can this even happen - or is U-APSD only for QoS STA?
>
> uAPSD can only be used by a QoS STA.
>
>> Then we would have to manually append a QoS Null with the EOSP flag +
>> TX_STATUS?
>>
>> So like this:
>>
>> /* set EOSP for the _last_ frame or appended a QoS Null when needed */
>> if (reason == IEEE80211_FRAME_RELEASE_UAPSD&&
>> skb_queue_empty(&frames)) {
>> if (qoshdr) {
>> *qoshdr |= IEEE80211_QOS_CTL_EOSP;
>>
>> info->flags |= IEEE80211_TX_STATUS_EOSP |
>> IEEE80211_TX_CTL_REQ_TX_STATUS;
>> } else {
>> ieee80211_send_null_response(sdata, tid, reason);
>> }
>> }
>
> No, I think it should be more like this:
>
>
> /* set EOSP for the frame */
>
> if (skb_queue_empty(&frames)) {
> if (reason == IEEE80211_FRAME_RELEASE_UAPSD&& qoshdr)
> *qoshdr |= IEEE80211_QOS_CTL_EOSP;
>
> info->flags |= IEEE80211_TX_STATUS_EOSP |
> IEEE80211_TX_CTL_REQ_TX_STATUS;
> }
Oh, yes, I see. In case of reason==IEEE80211_FRAME_RELEASE_PSPOLL, it is
intended to not send the EOSP, but still set IEEE80211_TX_STATUS_EOSP.
Who sends the patch?
Regards,
Marco
[-- Attachment #1.2: marco_porsch.vcf --]
[-- Type: text/x-vcard, Size: 432 bytes --]
begin:vcard
fn:Marco Porsch
n:Porsch;Marco
org:Chemnitz University of Technology;Communication Networks
adr;quoted-printable;quoted-printable:Fakult=C3=A4t f=C3=BCr Elektrotechnik und Informationstechnik , Professur=
Kommunikationsnetze;;Technische Universit=C3=A4t Chemnitz;Chemnitz;;D - 09107;Germany
email;internet:marco.porsch@etit.tu-chemnitz.de
title:Dipl.-Ing.
tel;work:+49 371 531 37523
version:2.1
end:vcard
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5088 bytes --]
next prev parent reply other threads:[~2012-03-16 13:58 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
2012-03-16 13:38 ` Marco Porsch
2012-03-16 13:40 ` Johannes Berg
2012-03-16 13:58 ` Marco Porsch [this message]
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=4F6346FE.4060005@etit.tu-chemnitz.de \
--to=marco.porsch@etit.tu-chemnitz.de \
--cc=johannes@sipsolutions.net \
--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).