From mboxrd@z Thu Jan  1 00:00:00 1970
From: Pavel Balaev <mail@void.so>
Subject: Re: [PATCH] ipv4: allow newer DSCP values in ip rules
Date: Tue, 20 Nov 2018 11:48:46 +0300
Message-ID: <20181120084844.GA16862@rnd.infotecs.ru>
References: <20181119090042.GA18247@rnd.infotecs.ru>
 <20181119.151129.775973936240461162.davem@davemloft.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Cc: netdev@vger.kernel.org
To: David Miller <davem@davemloft.net>
Return-path: <netdev-owner@vger.kernel.org>
Received: from forward105o.mail.yandex.net ([37.140.190.183]:42473 "EHLO
        forward105o.mail.yandex.net" rhost-flags-OK-OK-OK-OK)
        by vger.kernel.org with ESMTP id S1725866AbeKTTRk (ORCPT
        <rfc822;netdev@vger.kernel.org>); Tue, 20 Nov 2018 14:17:40 -0500
Content-Disposition: inline
In-Reply-To: <20181119.151129.775973936240461162.davem@davemloft.net>
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>

On Mon, Nov 19, 2018 at 03:11:29PM -0800, David Miller wrote:
> From: Pavel Balaev <mail@void.so>
> Date: Mon, 19 Nov 2018 12:00:45 +0300
> 
> > After this patch this one can use it: 
> 
> You can "configure it" but it doesn't work at all.
> 
> Did you test this in any way beyond simply dumping the FIB rule
> tables?
> 
> The whole kernel masks the TOS value using RT_TOS() so it is going to
> clear out those extra bits every time the configured value actually
> gets used.
Ok, I got it. I'll test RFC2597 values with full scheme and tries to
make it works.