[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20171031172754.56dc26af@shemminger-XPS-13-9360>
Date: Tue, 31 Oct 2017 17:27:54 +0100
From: Stephen Hemminger <stephen@...workplumber.org>
To: Amritha Nambiar <amritha.nambiar@...el.com>
Cc: netdev@...r.kernel.org, alexander.h.duyck@...el.com,
jiri@...nulli.us, jhs@...atatu.com, alexander.duyck@...il.com,
xiyou.wangcong@...il.com
Subject: Re: [iproute2, RFC PATCH] flower: Represent HW traffic classes as
classid values
On Fri, 27 Oct 2017 02:37:44 -0700
Amritha Nambiar <amritha.nambiar@...el.com> wrote:
> Use the classid values reserved in the range :ffe0 - :ffef
> to identify hardware traffic classes.
>
> Example:
> Match Dst IPv4,Dst Port and route to TC1:
> # tc filter add dev eth0 protocol ip parent ffff:\
> prio 1 flower dst_ip 192.168.1.1/32\
> ip_proto udp dst_port 12000 skip_sw\
> hw_tc 1
>
> # tc filter show dev eth0 parent ffff:
> filter pref 1 flower chain 0
> filter pref 1 flower chain 0 handle 0x1 hw_tc 1
> eth_type ipv4
> ip_proto udp
> dst_ip 192.168.1.1
> dst_port 12000
> skip_sw
> in_hw
>
> Signed-off-by: Amritha Nambiar <amritha.nambiar@...el.com>
Not sure. Using reserved values can lead to future problems, but this
might be only simple way to handle this.
Powered by blists - more mailing lists