[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1373563030.2085.14.camel@bwh-desktop.uk.level5networks.com>
Date: Thu, 11 Jul 2013 18:17:10 +0100
From: Ben Hutchings <bhutchings@...arflare.com>
To: Cedric Debarge <cedric.debarge@...sys.fr>
CC: <netdev@...r.kernel.org>, <linux-wireless@...r.kernel.org>
Subject: Re: [RFC]: vlan priority handling in WMM
On Thu, 2013-07-11 at 09:45 +0200, Cedric Debarge wrote:
> Dear mailing list,
>
> I would like to manage the VLAN priority in Wireless QOS (WMM).
>
> I get the VLAN tag from skb->vlan_tci and I extract the VLAN priority.
>
> How I should handle the priority value 0.
> - Handle this value as no priority request, In this case the frame will
> sent with the DSCP priority or default (Best effort)
> - Handle this value as a lowest priority, in this case I Map it to the WMM.
[...]
IEEE 802.1q refers to the definition in 802.1d:
> The user_priority parameter is the priority requested by the
> originating service user. The value of this parameter is in the range
> 0 through 7.
>
> NOTEāThe default user_priority value is 0. Values 1 through 7 form an
> ordered sequence of user_priorities, with 1 being the lowest value and
> 7 the highest. See 7.7.3 and Annex G (informative) for further
> explanation of the use of user_priority values.
So a value of 0 should be treated as no priority request, same as for an
untagged frame.
Ben.
--
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists