[dpdk-dev] [RFC] ethdev: add IPv4/IPv6 DSCP rewrite action

[Stephen Hemminger]

On Tue, 10 Dec 2019 08:55:40 +0000
Suanming Mou <suanmingm at mellanox.com> wrote:

> > -----Original Message-----
> > From: Andrew Rybchenko <arybchenko at solarflare.com>
> > Sent: Tuesday, December 10, 2019 3:33 PM
> > To: Suanming Mou <suanmingm at mellanox.com>; Adrien Mazarguil
> > <adrien.mazarguil at 6wind.com>; John McNamara <john.mcnamara at intel.com>;
> > Marko Kovacevic <marko.kovacevic at intel.com>; Thomas Monjalon
> > <thomas at monjalon.net>; Ferruh Yigit <ferruh.yigit at intel.com>
> > Cc: dev at dpdk.org; Shahaf Shuler <shahafs at mellanox.com>; Ori Kam
> > <orika at mellanox.com>; Matan Azrad <matan at mellanox.com>; Slava Ovsiienko
> > <viacheslavo at mellanox.com>
> > Subject: Re: [dpdk-dev] [RFC] ethdev: add IPv4/IPv6 DSCP rewrite action
> > 
> > On 12/10/19 8:23 AM, Suanming Mou wrote:  
> > > For some overlay network, such as VXLAN, the DSCP field in the new
> > > outer IP header after VXLAN decapsulation may need to be updated  
> > accordingly.  
> > >
> > > This commit introduce the DSCP modify action for IPv4 and IPv6.
> > >
> > > Signed-off-by: Suanming Mou <suanmingm at mellanox.com>  
> > 
> > Acked-by: Andrew Rybchenko <arybchenko at solarflare.com>
> > 
> > as usual it requires testpmd support and a driver which supports it (I understand
> > that it may be omitted in RFC).  
> 
> Thanks. Yes, it will be added later.

Then this patch must not be applied until one or more drivers is ready to use it.
Very easy to get API and semantics wrong, until it is there.