mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ahmed Abdelsalam <ahabdels@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: kuznet@ms2.inr.ac.ru, yoshfuji@linux-ipv6.org, kuba@kernel.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	andrea.mayer@uniroma2.it
Subject: Re: [net-next v4] seg6: using DSCP of inner IPv4 packets
Date: Tue, 25 Aug 2020 14:01:27 +0200	[thread overview]
Message-ID: <e8f49be9-f658-e863-3359-c28f122dc382@gmail.com> (raw)
In-Reply-To: <20200824.181109.421299456838417383.davem@davemloft.net>



On 25/08/2020 03:11, David Miller wrote:
> From: Ahmed Abdelsalam <ahabdels@gmail.com>
> Date: Mon, 24 Aug 2020 08:51:24 +0000
> 
>> This patch allows copying the DSCP from inner IPv4 header to the
>> outer IPv6 header, when doing SRv6 Encapsulation.
>>
>> This allows forwarding packet across the SRv6 fabric based on their
>> original traffic class.
>>
>> Signed-off-by: Ahmed Abdelsalam <ahabdels@gmail.com>
> 
> "Allows" sounds like the behavior is optional, but that is not what
> is happening here.  You are making this DSCP inheritance behavior
> unconditional.
> 
> I've stated that the current behavior matches what other ipv6
> tunneling devices do, and therefore we should keep it that way.
> 
> Furthermore, this behavior has been in place for several releases
> so you cannot change it by default.  People may be depending upon
> how things work right now.
> 

Ok. I added a new sysctl (seg6_inherit_inner_ipv4_dscp) to 
enable/disable the new behavior.

The sysctl will be checked in case of IPv4 traffic.
In the IPv6 case, there is no change as the code is already copying the 
DSCP from the inner IPv6 packet.

I'm sending a new patch.


> Also:
> 
>> @@ -130,6 +129,7 @@ int seg6_do_srh_encap(struct sk_buff *skb, struct ipv6_sr_hdr *osrh, int proto)
>>   	struct ipv6_sr_hdr *isrh;
>>   	int hdrlen, tot_len, err;
>>   	__be32 flowlabel;
>> +	u8 tos = 0, hop_limit;
> 
> Need to preserve reverse christmas tree here.
> 
Fixed in the new patch.

      reply	other threads:[~2020-08-25 12:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-24  8:51 Ahmed Abdelsalam
2020-08-25  1:11 ` David Miller
2020-08-25 12:01   ` Ahmed Abdelsalam [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e8f49be9-f658-e863-3359-c28f122dc382@gmail.com \
    --to=ahabdels@gmail.com \
    --cc=andrea.mayer@uniroma2.it \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=yoshfuji@linux-ipv6.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome