1 // SPDX-License-Identifier: GPL-2.0
12  * IEEE 802.1Q-2022 in Annex I "I.3 Traffic type to traffic class mapping" and
13  * Table I-1 "Traffic type to traffic class mapping".
82  * ieee8021q_tt_to_tc - Map IEEE 802.1Q Traffic Type to Traffic Class
87  * on the number of queues configured on the NIC. The mapping is based on the
88  * example provided by IEEE 802.1Q-2022 in Annex I "I.3 Traffic type to traffic
89  * class mapping" and Table I-1 "Traffic type to traffic class mapping".
99 		return -EINVAL;  in ieee8021q_tt_to_tc()
105 				   IEEE8021Q_TT_MAX - 1,  in ieee8021q_tt_to_tc()
106 				   "ieee8021q_8queue_tt_tc_map != max - 1");  in ieee8021q_tt_to_tc()
110 				   IEEE8021Q_TT_MAX - 1,  in ieee8021q_tt_to_tc()
111 				   "ieee8021q_7queue_tt_tc_map != max - 1");  in ieee8021q_tt_to_tc()
116 				   IEEE8021Q_TT_MAX - 1,  in ieee8021q_tt_to_tc()
117 				   "ieee8021q_6queue_tt_tc_map != max - 1");  in ieee8021q_tt_to_tc()
122 				   IEEE8021Q_TT_MAX - 1,  in ieee8021q_tt_to_tc()
123 				   "ieee8021q_5queue_tt_tc_map != max - 1");  in ieee8021q_tt_to_tc()
128 				   IEEE8021Q_TT_MAX - 1,  in ieee8021q_tt_to_tc()
129 				   "ieee8021q_4queue_tt_tc_map != max - 1");  in ieee8021q_tt_to_tc()
134 				   IEEE8021Q_TT_MAX - 1,  in ieee8021q_tt_to_tc()
135 				   "ieee8021q_3queue_tt_tc_map != max - 1");  in ieee8021q_tt_to_tc()
140 				   IEEE8021Q_TT_MAX - 1,  in ieee8021q_tt_to_tc()
141 				   "ieee8021q_2queue_tt_tc_map != max - 1");  in ieee8021q_tt_to_tc()
146 				   IEEE8021Q_TT_MAX - 1,  in ieee8021q_tt_to_tc()
147 				   "ieee8021q_1queue_tt_tc_map != max - 1");  in ieee8021q_tt_to_tc()
154 	return -EINVAL;  in ieee8021q_tt_to_tc()
159  * ietf_dscp_to_ieee8021q_tt - Map IETF DSCP to IEEE 802.1Q Traffic Type
163  * Since there is no corresponding mapping between DSCP and IEEE 802.1Q Traffic
165  * the mapping between DSCP and 802.11 User Priority (UP) values.
174 	 * [RFC4594], Section 4.8, recommends High-Throughput Data be marked  in ietf_dscp_to_ieee8021q_tt()
178 	 * By default (as described in Section 2.3), High-Throughput Data will  in ietf_dscp_to_ieee8021q_tt()
182 	 * Unfortunately, there really is no corresponding fit for the High-  in ietf_dscp_to_ieee8021q_tt()
183 	 * Throughput Data service class within the constrained 4 Access  in ietf_dscp_to_ieee8021q_tt()
184 	 * Category [IEEE.802.11-2016] model.  If the High-Throughput Data  in ietf_dscp_to_ieee8021q_tt()
186 	 * then it would contend with Low-Latency Data (while [RFC4594]  in ietf_dscp_to_ieee8021q_tt()
190 	 * receive a less-then-best-effort service and contend with Low-Priority  in ietf_dscp_to_ieee8021q_tt()
191 	 * Data (as discussed in Section 4.2.10).  in ietf_dscp_to_ieee8021q_tt()
193 	 * As such, since there is no directly corresponding fit for the High-  in ietf_dscp_to_ieee8021q_tt()
194 	 * Throughout Data service class within the [IEEE.802.11-2016] model, it  in ietf_dscp_to_ieee8021q_tt()
195 	 * is generally RECOMMENDED to map High-Throughput Data to UP 0, thereby  in ietf_dscp_to_ieee8021q_tt()
198 	 * Note: The above text is from RFC8325 which is describing the mapping  in ietf_dscp_to_ieee8021q_tt()
199 	 * between DSCP and 802.11 User Priority (UP) values. The mapping  in ietf_dscp_to_ieee8021q_tt()
209 	 * RFC3662 and RFC4594 both recommend Low-Priority Data be marked  in ietf_dscp_to_ieee8021q_tt()
210 	 * with DSCP CS1. The Low-Priority Data service class loosely  in ietf_dscp_to_ieee8021q_tt()
211 	 * corresponds to the [IEEE.802.11-2016] Background Access Category  in ietf_dscp_to_ieee8021q_tt()