From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id A90C73B29D for ; Wed, 5 Jan 2022 07:28:56 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gmx.net; s=badeba3b8450; t=1641385731; bh=JATqP8wTq6tAWiLAXoUMLkijESNDR+aH9Mn/Kfa5NIA=; h=X-UI-Sender-Class:Subject:From:In-Reply-To:Date:Cc:References:To; b=cWhDescvlbvPv5A6qTFqIcICt1Q1oNvzWmbZECUyEFgJ9sOtaZPtBKKVrXXaffD8N 0GPu++IJAjNj7dJsDRrC1rR5dQoUh38YR2Yw3Rem5modvFq686xD+KUbpue9TaePdi g31nhHzyMVI3W4ImU90CR5l6mNTK19yNTEgqeavk= X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c Received: from smtpclient.apple ([134.76.241.253]) by mail.gmx.net (mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id 1MkHMZ-1mgV6g1bGz-00kcb2; Wed, 05 Jan 2022 13:28:51 +0100 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\)) From: Sebastian Moeller In-Reply-To: <87k0febdaq.fsf@toke.dk> Date: Wed, 5 Jan 2022 13:28:48 +0100 Cc: Jon Pike , make-wifi-fast@lists.bufferbloat.net Content-Transfer-Encoding: quoted-printable Message-Id: References: <87r19nb27v.fsf@toke.dk> <87k0febdaq.fsf@toke.dk> To: =?utf-8?Q?Toke_H=C3=B8iland-J=C3=B8rgensen?= X-Mailer: Apple Mail (2.3654.120.0.1.13) X-Provags-ID: V03:K1:wE8SK+IJLGYjZPY94aJqEXWcuk0kbfkPx+8GL4Z1gZUbgf6pp/g gr0xjFThDVr5m9rj8H/SuJgls4k6WiIJsognJNlgXOxRfOSws2op0bw/2V84zM2anJXXhJ3 61l7pvdVTLESTIzc7FgyVebVrR13JuneUYeRnLR83AKUJnQ+QcV/t8cVhnClUsIdQHgSp7q xuyH+SoeCKF/OtMkGtDsQ== X-Spam-Flag: NO X-UI-Out-Filterresults: notjunk:1;V03:K0:BLxxN0cWC8s=:fkeg+j7lFvjoN+nA22SalV JCnIOqIiEmGd0j3lUhy5dLbMxAC2847gT/TC3qZj9XkpxyYE+fpokdlkwjjFDhj0Vr+HeiHlC Fb4ApwR2oZc5f9eyaytj2j7hpG2hK0d+Ri7GPy6tXkETEVi6BIG4Iif/6Ho6bGkKVhZQ8sOhV bfrEVPgjkuKJ7FIPdSar/fWbaRlYj0niD5A8YNfX2sh/4Vb1M0/sAC2TSwSubJ/W87cBNAiCA An1nWf3MdVWrj2C/qL+MC59h6Vvv56w03zMgo1z8BZbuxpj7HBAQltZe0SP2SGobZZ+wy9bfW QZAqYZAoBK9wTchOM8x05DSYxHtaXjRtNBAcAoRh6PdHalFx1v1NA0HKXkbVl62ei0yPUrR0H GfIobdKxPG8LcXevySO1ubzTqz39yR2xAguFMK/pQjCVFY1dul+wUTF6VVujZyT1ypaM1C8Hs p+aN/uB7JSf/pE2xl/vjdDrM866uVgIN2goXnIMSmK5bvXxh+xQmDEWSPmWKo4ED0Vkji8Yuv uleY020g1+ZXoTfQnOERP0hEz6jf5zjY9gmQ7afQCPfV2BHafVqQIPeHq84foKUWDSWOYxF/l PnaywJb04t2bPGsETRW0q2v1Da13dXcyQkF7m0UegILZo3WxMEgkiY828FOK/vOamdw0OtiA8 ZzrMtiSPL+EP7wi5+XzRz0MfuHA4zW/4LfKdafULY2m09owWwWAeV1dkuIaR6ZffRbc2vDqam V4dfYtZS/aYxU5JK08pjsqQyuUqvcJazxUJN7wUy1gmlFnlZfsDXNGaJjr8Z9qxgMLU/q0r0l T/xSl838mzPMhjt6EC60RxdlKfLQkMBUiA8wT0pA813TY/c44af88yc5rrwfqcLp2nIQF0b5v 84sVBfLu60JniXbRhPzYk/vhh0lWXmGIAkl+/psHU53O8xV+8koPgJycEhzqzIOKZMuZrtFfz VA/HijgDxyuzlAo9YDFyB85P21gcaP220Zyac3cSwPL/YhAbA9Ffapa9prTkUK+JI3xai9PB/ FgH0DEGbBB/3B9r3xV7Q+2oSLKNv9G82IJjhS+h48bBMu3SFSXreYRIlgjuX747KktxkvCI22 oDWf2ZeVcGA6c4= Subject: Re: [Make-wifi-fast] Upcoming WiFi standard to set per-flow DSCP values? X-BeenThere: make-wifi-fast@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jan 2022 12:28:57 -0000 Hi Toke, hi Jon, here is a corrected version of what I sent to another list (I = accidentally converted the VA bit-pattern with my calculator set to = base8 so decimal 54 and Range7 instead of the correct decimal 44 and = Range6, which does not change much for the AC mapping as both range6 and = 7 map to AC_VO): >> hostapd: add wmm qos map set by default >> author Felix Fietkau =09 >> Wed, 3 Nov 2021 22:40:53 +0100 (22:40 +0100) >> committer Felix Fietkau =09 >> Wed, 3 Nov 2021 22:47:55 +0100 (22:47 +0100) >> commit a5e3def1822431ef6436cb493df77006dbacafd6 >> tree f4494efd6e08a872524eedb5081564a6f5ece20c tree | snapshot >> parent b14f0628499142a718a68be7d1a7243f7f51ef0a commit | = diff >> hostapd: add wmm qos map set by default >>=20 >> This implements the mapping recommendations from RFC8325, with an >> update from RFC8622. This ensures that DSCP marked packets are = properly >> sorted into WMM classes. >> The map can be disabled by setting iw_qos_map_set to something = invalid >> like 'none' >>=20 >> Signed-off-by: Felix Fietkau >=20 > Which introduces the following new RFC8325 inspired DSCP to AC = mappings: > + set_default iw_qos_map_set = 0,0,2,16,1,1,255,255,18,22,24,38,40,40,44,46,48,56 >=20 > Which translates into the following mappings (according to the hostapd = rules below*): >=20 > unraveling this gets us to (0 is coded as DSCP Exception, the rest as = DSCP ranges): >=20 > UP DSCP AC PHBs(decDSCP) > Ex0 BE BE(0) BE/CS0(0) > Range0 2-16 BE CS1(8)**, AF11(10), AF12(12), AF13(14), = CS2(16) > Range1 1-1 BK LE(1) > Range2 -=09 > Range3 18-22 BE AF21(18), AF22(20), AF23(22) > Range4 24-38 VI CS3(24), AF31(26), AF32(28), AF33(30), = CS4(32), AF41(34), AF42(36), AF43(38) > Range5 40-40 VI CS5(40) > Range6 44-46 VO VA(44), EF(46) > Range7 48-56 VO CS6(48), CS7(56) The kernel's default mappings, as far as = https://wireless.wiki.kernel.org/en/developers/documentation/mac80211/queu= es states, seem driven by the top 3 bits of the DSCP field: RFC8325 also has a section about the default mappings UP DSCP AC PHBs(decDSCP) Range0 0-7 BE CS0(0) Range1 8-15 BK CS1(8), AF11(10), AF12(12), AF13(14) Range2 16-23 BK CS2(16), AF21(18), AF22(20), AF23(22) Range3 24-31 BE CS3(24), AF31(26), AF32(28), AF33(30) Range4 32-39 VI CS4(32), AF41(34), AF42(36), AF43(38) Range5 40-47 VI CS5(40), VA(44), EF(46) Range6 48-55 VO CS6(48) Range7 56-63 VO CS7(56) IMHO RFC8325 and the whole WMM scheme clearly lacks data showing that is = actually delivers on its promises. RFC8325 specifically seems obsessed = in changing mappings such that PHBs align with the 4 WMM queues, instead = of interpreting the fact that the apparent mismatch between what the = IETF thinks about specific PHBs/DSCPs and how they are treated for most = users, as clear sign, that reality does not care... (probably mostly = driven by the elephant in the room, of DSCPs not being end-to-end). I agree with Toke that allowing APs to steer specific DSCP use by = applications seems taking an proven non-working idea to the extreme... = (APs can already instruct stations on which DSCPs to map to which AC = (see Felix's patch), which is not used that much, no idea why anybody = thinks that allowing APs even more disruptive changes to end-point = behavior is going to work any better). Regards Sebastian P.S.: IMHO the biggest change might be the up-prioritisation of EF from = AC_VI to AC_VO, and I am not sure that is a good idea. > On Jan 5, 2022, at 13:02, Toke H=C3=B8iland-J=C3=B8rgensen via = Make-wifi-fast wrote: >=20 > Jon Pike writes: >=20 >> Heh... So each and everyone in the stadium can have ALL their data >> prioritized above everybody else's! For a more Egalitarian world! >>=20 >> Sigh... Meanwhile, back in reality... >>=20 >> An aside, is that commit in git a significant improvement on the = mappings, >> or just some minor tweaks? >=20 > I *think* they are just minor tweaks, but I don't actually recall the > exact mapping that's the kernel default... >=20 > -Toke > _______________________________________________ > Make-wifi-fast mailing list > Make-wifi-fast@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/make-wifi-fast