From: Sebastian Gottschall <s.gottschall@dd-wrt.com>
To: ath10k@lists.infradead.org
Subject: Re: WMM not working for mcast packets on ath10k
Date: Tue, 11 Aug 2020 14:14:55 +0200 [thread overview]
Message-ID: <bbc46d8f-1f10-6c99-24d4-10e0d713b23b@dd-wrt.com> (raw)
In-Reply-To: <7bdee5c8-c271-0902-510c-d8a41b7ec4b8@candelatech.com>
Am 11.08.2020 um 01:05 schrieb Ben Greear:
> On 8/10/20 3:08 PM, Ahmed Zaki wrote:
>> Hello,
>>
>> I have 2 ath10k devices set in Mesh Point mode. When I use iptables'
>> DSCP target to set the WMM AC for some traffic ports to VO, the rules
>> work fine but only for unicast packets. All broadcast on the target
>> UDP ports goes out as BE, and not VO.
>>
>> With some ath10k debugging enabled, it seems that the htt is indeed
>> sending the tx descriptor with the correct tid (6) set.
>>
>> Is this the intended behavior for some reason? If not, is there any
>> more debugging on the TX path that I can do?
>
> I don't think that WMM makes sense for bcast frames since they go out on
> a special TID that does not do aggregation or per peer QoS settings.
and in addition broadcast frames are transmitted with legacy rates (2
mbit by default, but can be changed)
>
> Thanks,
> Ben
>
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2020-08-11 12:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-10 22:08 WMM not working for mcast packets on ath10k Ahmed Zaki
2020-08-10 23:05 ` Ben Greear
2020-08-11 12:14 ` Sebastian Gottschall [this message]
2020-08-11 12:22 ` Ahmed Zaki
2020-08-11 14:01 ` Ben Greear
2020-08-11 14:36 ` Ahmed Zaki
2020-08-11 14:39 ` Ben Greear
2020-08-12 13:09 ` Ahmed Zaki
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=bbc46d8f-1f10-6c99-24d4-10e0d713b23b@dd-wrt.com \
--to=s.gottschall@dd-wrt.com \
--cc=ath10k@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.