From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.toke.dk X-Spam-Level: X-Spam-ASN: AS60781 77.235.32.0/19 X-Spam-Status: No, score=-101.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE, SHORTCIRCUIT shortcircuit=ham autolearn=disabled version=3.4.1 Received: from mail.toke.dk by mail.toke.dk with LMTP id 9copI4+YjVtDZQAAOr1fkg (envelope-from ) for ; Mon, 03 Sep 2018 22:24:47 +0200 Received: from web6.sd.eurovps.com (web6.sd.eurovps.com [77.235.54.103]) by mail.toke.dk (Postfix) with ESMTPS id 6585B4B618E for ; Mon, 3 Sep 2018 22:24:46 +0200 (CEST) Authentication-Results: mail.toke.dk; dkim=fail reason="key not found in DNS" (0-bit key) header.d=flent.org header.i=@flent.org header.b=erv7povC; dkim=fail reason="signature verification failed" (1024-bit key) header.d=github.com header.i=@github.com header.b=LFgeZYxV DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=flent.org; s=default; h=Sender:Content-Type:Cc:Reply-To:List-Subscribe:List-Help: List-Post:List-Archive:List-Unsubscribe:List-Id:Subject:Mime-Version: References:In-Reply-To:Message-ID:To:From:Date:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=iko20HEk8G6tLGxp+a/bHFp17+QFAxGABFyqzAKCSMY=; b=erv7povCUf3z0gAY+vTE9WE6NW 2sWvWgVVbQE7ZLhEr0xXYsccOEXyu/QOpUWAcKzKJnTPyEjKnrNOZKRWjhlH4hHGf7ZxLZcYkmXRx 1rhLFtAkOb+uV+qQuMHE4IR3QBbY/6GRuYoFNj+ZYl5eofMmkeNs8bqn+Q6lf9EFCo+QLFkghEY5v wBuAnJSnZIhumDsEd83jtKBTEw8VDOSB2D6iWK6XEt588zNRC7K1XjQ21/SRxVU35+R9EMBztJ5rc f+SQ3Mpcbqqbt4YxY+WqBD/9IN1C/81YwFpgOlbS5efmwXRVmXBa9tyu+6JFl1mt209+41KMvEBmm R09eD7mA==; Received: from [::1] (port=36950 helo=web6.sd.eurovps.com) by web6.sd.eurovps.com with esmtp (Exim 4.91) (envelope-from ) id 1fwvOu-006lhF-VK; Mon, 03 Sep 2018 23:24:44 +0300 Received: from out-15.smtp.github.com ([192.30.254.198]:59837) by web6.sd.eurovps.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91) (envelope-from ) id 1fwvOq-006lVb-FY for flent-users@flent.org; Mon, 03 Sep 2018 23:24:43 +0300 Date: Mon, 03 Sep 2018 13:23:58 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1536006239; bh=Af2MUg1zdJwvIxbtf0zn9ox5U27VccbpT1kJAyiHaxY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=LFgeZYxVm3tfpTYUrcW28rmepRhRq+hpv48gcI6OuVap7FHQVRAl7FzGWov4xxUo2 Kfsm+8MoyVGYBJSSVPs8f4HH4aveRarMSpc4nJHoIMWK6i4g49r7HLXUrzq2WA7Tb/ O0g4maJb+OMdScbjfjX0xq79TmCPi/MY+3r1dxLI= From: =?UTF-8?B?VG9rZSBIw7hpbGFuZC1Kw7hyZ2Vuc2Vu?= To: tohojo/flent Message-ID: In-Reply-To: References: Mime-Version: 1.0 Precedence: list X-GitHub-Sender: tohojo X-GitHub-Recipient: flent-users X-GitHub-Reason: comment X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: flent-users@flent.org Subject: Re: [Flent-users] [tohojo/flent] testing the behavior of small queue building non-ecn'd flows (#148) X-BeenThere: flent-users@flent.org X-Mailman-Version: 2.1.26 List-Id: Flent discussion list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: tohojo/flent Cc: Comment , flent-users Content-Type: multipart/mixed; boundary="===============1929795783466930238==" Errors-To: flent-users-bounces@flent.org Sender: "Flent-users" X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - web6.sd.eurovps.com X-AntiAbuse: Original Domain - toke.dk X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - flent.org X-Get-Message-Sender-Via: web6.sd.eurovps.com: acl_c_authenticated_local_user: mailman/mailman X-Authenticated-Sender: web6.sd.eurovps.com: mailman@flent.org --===============1929795783466930238== Content-Type: multipart/alternative; boundary="--==_mimepart_5b8d985ed84c5_69853ff87c2d45c4218885"; charset=UTF-8 Content-Transfer-Encoding: 7bit ----==_mimepart_5b8d985ed84c5_69853ff87c2d45c4218885 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable flent-users writes: > HI Toke, > > >> On Sep 3, 2018, at 19:37, Toke H=C3=B8iland-J=C3=B8rgensen wrote: >> = >> flent-users writes: >> = >> > Hi Dave, >> > >> > >> >> On Sep 3, 2018, at 18:00, Dave T=C3=A4ht = wrote: >> >> vnv = >> >> Another rrul_v2 issue would be to correctly end up in all the queue= s on wifi. >> > >> > So in theory rrul_cs8 should do that... (it aims to just use one >> > dscp-marked flow per class selector for a total of 8 tcp flows per >> > direction...) In practice I believe the mapping from dscps to ACs is= >> > highly non-linear... >> = >> Well, not that non-linear: >> = >> const int ieee802_1d_to_ac[8] =3D { >> IEEE80211_AC_BE, >> IEEE80211_AC_BK, >> IEEE80211_AC_BK, >> IEEE80211_AC_BE, >> IEEE80211_AC_VI, >> IEEE80211_AC_VI, >> IEEE80211_AC_VO, >> IEEE80211_AC_VO >> }; > > Well, aren't these values according to IEEE P802.1p (https://en.wikiped= ia.org/wiki/IEEE_P802.1p)? > > PCP value Priority Acronym Traffic types > 1 0 (lowest) BK Background > 0 1 (default) BE Best effort > 2 2 EE Excellent effort > 3 3 CA Critical applications > 4 4 VI Video, < 100 ms latency and jitter > 5 5 VO Voice, < 10 ms latency and jitter > 6 6 IC Internetwork control > 7 7 (highest) NC Network control > > These map the 3 bit priority PCP values from VLAN tags to ACs, but > note the dance with PCP 1 being lower than PCP 0, and more importantly > the different interpretations about PCP 2, is it "excellent effort" or > another BK code point? > > I guess the point I wanted to make is that mapping down from the 6bit > DSCP to ACs is not very intuitive (with linear mapping being the "most > intuitive"). > > Anyway, I am totally fine with just using 3 bits, this is still plenty > for priority hierarchies that I can still understand ;) Oh, it's absolutely a mess. So much so that the IETF had to write a whole RFC on it: https://tools.ietf.org/html/rfc8325 -Toke -- = You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/tohojo/flent/issues/148#issuecomment-418188201= ----==_mimepart_5b8d985ed84c5_69853ff87c2d45c4218885 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable flent-users <notifications@github.com> writes:

> HI Toke,
>
>
>> On Sep 3, 2018, at 19:37, Toke H=C3=B8iland-J=C3=B8rgensen <n= otifications@github.com> wrote:
>>
>> flent-users <notifications@github.com> writes:
>>
>> > Hi Dave,
>> >
>> >
>> >> On Sep 3, 2018, at 18:00, Dave T=C3=A4ht <notificati= ons@github.com> wrote:
>> >> vnv
>> >> Another rrul_v2 issue would be to correctly end up in a= ll the queues on wifi.
>> >
>> > So in theory rrul_cs8 should do that... (it aims to just us= e one
>> > dscp-marked flow per class selector for a total of 8 tcp fl= ows per
>> > direction...) In practice I believe the mapping from dscps = to ACs is
>> > highly non-linear...
>>
>> Well, not that non-linear:
>>
>> const int ieee802_1d_to_ac[8] =3D {
>> IEEE80211_AC_BE,
>> IEEE80211_AC_BK,
>> IEEE80211_AC_BK,
>> IEEE80211_AC_BE,
>> IEEE80211_AC_VI,
>> IEEE80211_AC_VI,
>> IEEE80211_AC_VO,
>> IEEE80211_AC_VO
>> };
>
> Well, aren't these values according to IEEE P802.1p (https://en.= wikipedia.org/wiki/IEEE_P802.1p)?
>
> PCP value Priority Acronym Traffic types
> 1 0 (lowest) BK Background
> 0 1 (default) BE Best effort
> 2 2 EE Excellent effort
> 3 3 CA Critical applications
> 4 4 VI Video, < 100 ms latency and jitter
> 5 5 VO Voice, < 10 ms latency and jitter
> 6 6 IC Internetwork control
> 7 7 (highest) NC Network control
>
> These map the 3 bit priority PCP values from VLAN tags to ACs, but > note the dance with PCP 1 being lower than PCP 0, and more important= ly
> the different interpretations about PCP 2, is it "excellent eff= ort" or
> another BK code point?
>
> I guess the point I wanted to make is that mapping down from the 6bi= t
> DSCP to ACs is not very intuitive (with linear mapping being the &qu= ot;most
> intuitive").
>
> Anyway, I am totally fine with just using 3 bits, this is still plen= ty
> for priority hierarchies that I can still understand ;)

Oh, it's absolutely a mess. So much so that the IETF had to write a whole RFC on it: https://tools.ietf.org/html/rfc8325

-Toke

&m= dash;
You are receiving this because you commented.
Reply to th= is email directly, view it on GitHub, or mute the thread.3D""

= ----==_mimepart_5b8d985ed84c5_69853ff87c2d45c4218885-- --===============1929795783466930238== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Flent-users mailing list Flent-users@flent.org http://flent.org/mailman/listinfo/flent-users_flent.org --===============1929795783466930238==--