From: "Arend van Spriel" <arend@broadcom.com>
To: "David Shwatrz" <dshwatrz@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Question about ieee802_1d_to_ac
Date: Tue, 16 Oct 2012 15:00:01 +0200 [thread overview]
Message-ID: <507D5A51.3040400@broadcom.com> (raw)
In-Reply-To: <CAJJAcodOQY6PDp6d=jG30u_7B30G3j8xOrtLQVmEJ4TDYjh_xQ@mail.gmail.com>
On 10/16/2012 10:04 AM, David Shwatrz wrote:
> Hello,
>
> I see in net/mac80211/wme.c:
> ...
> const int ieee802_1d_to_ac[8] = {
> IEEE80211_AC_BE,
> IEEE80211_AC_BK,
> IEEE80211_AC_BK,
> IEEE80211_AC_BE,
> IEEE80211_AC_VI,
> IEEE80211_AC_VI,
> IEEE80211_AC_VO,
> IEEE80211_AC_VO
> };
> ...
This is the correct mapping if you want to trust the IEEE802.11e
standard (Table 20i).
Gr. AvS
> As I understand, this values stand for queues for different types of traffic:
> IEEE80211_AC_BE is best-effort traffic ,
> IEEE80211_AC_BK is background traffic ,
> IEEE80211_AC_VI is video traffic,
> IEEE80211_AC_VO is voice traffic.
>
> We see that entries 6,7 are voice and entries 4,5 are video.
> Is it not an error that entries 2,3 differ ? and also 0,1 ?
>
> shouldn't it be:
> const int ieee802_1d_to_ac[8] = {
> IEEE80211_AC_BE,
> IEEE80211_AC_BE,
> IEEE80211_AC_BK,
> IEEE80211_AC_BK,
>
>
> Regards,
> D Shwartz
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2012-10-16 13:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-16 8:04 Question about ieee802_1d_to_ac David Shwatrz
2012-10-16 13:00 ` Arend van Spriel [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=507D5A51.3040400@broadcom.com \
--to=arend@broadcom.com \
--cc=dshwatrz@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;
as well as URLs for NNTP newsgroup(s).