[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20160608164659.695ce9c5@xeon-e3>
Date: Wed, 8 Jun 2016 16:46:59 -0700
From: Stephen Hemminger <shemming@...cade.com>
To: Sridhar Samudrala <sridhar.samudrala@...el.com>
CC: <john.r.fastabend@...el.com>, <jakub.kicinski@...ronome.com>,
<netdev@...r.kernel.org>
Subject: Re: [PATCH v2 iproute2] tc: f_u32: Add support for skip_hw and
skip_sw flags
On Wed, 8 Jun 2016 16:16:01 -0700
Sridhar Samudrala <sridhar.samudrala@...el.com> wrote:
> On devices that support TC U32 offloads, these flags enable a filter to be
> added only to HW or only to SW. skip_sw and skip_hw are mutually exclusive
> flags. By default without any flags, the filter is added to both HW and SW,
> but no error checks are done in case of failure to add to HW.
> With skip-sw, failure to add to HW is treated as an error.
>
> Here is a sample script that adds 2 filters, one with skip_sw and the other
> with skip_hw flag.
>
> # add ingress qdisc
> tc qdisc add dev p4p1 ingress
>
> # enable hw tc offload.
> ethtool -K p4p1 hw-tc-offload on
>
> # add u32 filter with skip-sw flag.
> tc filter add dev p4p1 parent ffff: protocol ip prio 99 \
> handle 800:0:1 u32 ht 800: flowid 800:1 \
> skip-sw \
> match ip src 192.168.1.0/24 \
> action drop
>
> # add u32 filter with skip-hw flag.
> tc filter add dev p4p1 parent ffff: protocol ip prio 99 \
> handle 800:0:2 u32 ht 800: flowid 800:2 \
> skip-hw \
> match ip src 192.168.2.0/24 \
> action drop
>
> Signed-off-by: Sridhar Samudrala <sridhar.samudrala@...el.com>
Applied, then updated, already needed to cleanup some style issues in f_u32 anyway.
Powered by blists - more mailing lists