From: David Ahern <dsahern@gmail.com>
To: Jiri Pirko <jiri@resnulli.us>
Cc: netdev@vger.kernel.org, davem@davemloft.net, jhs@mojatatu.com,
xiyou.wangcong@gmail.com, jakub.kicinski@netronome.com,
simon.horman@netronome.com, john.hurley@netronome.com,
mlxsw@mellanox.com, sridhar.samudrala@intel.com
Subject: Re: [patch net-next v2 0/9] net: sched: introduce chain templates support with offloading to mlxsw
Date: Thu, 28 Jun 2018 09:10:45 -0600 [thread overview]
Message-ID: <1dbc630d-2da3-afbe-18ba-e9dfc893bf04@gmail.com> (raw)
In-Reply-To: <20180628142909.GE2177@nanopsycho.orion>
On 6/28/18 8:29 AM, Jiri Pirko wrote:
> Thu, Jun 28, 2018 at 04:18:47PM CEST, dsahern@gmail.com wrote:
>> On 6/28/18 7:08 AM, Jiri Pirko wrote:
>>> Create dummy device with clsact first:
>>> # ip link add type dummy
>>> # tc qdisc add dev dummy0 clsact
>>>
>>> There is no template assigned by default:
>>> # tc chaintemplate show dev dummy0 ingress
>>>
>>> Add a template of type flower allowing to insert rules matching on last
>>> 2 bytes of destination mac address:
>>> # tc chaintemplate add dev dummy0 ingress proto ip flower dst_mac 00:00:00:00:00:00/00:00:00:00:FF:FF
>>>
>>> The template is now showed in the list:
>>> # tc chaintemplate show dev dummy0 ingress
>>> chaintemplate flower chain 0
>>> dst_mac 00:00:00:00:00:00/00:00:00:00:ff:ff
>>> eth_type ipv4
>>>
>>> Add another template, this time for chain number 22:
>>> # tc chaintemplate add dev dummy0 ingress proto ip chain 22 flower dst_ip 0.0.0.0/16
>>> # tc chaintemplate show dev dummy0 ingress
>>> chaintemplate flower chain 0
>>> dst_mac 00:00:00:00:00:00/00:00:00:00:ff:ff
>>> eth_type ipv4
>>> chaintemplate flower chain 22
>>> eth_type ipv4
>>> dst_ip 0.0.0.0/16
>>>
>>> Add a filter that fits the template:
>>> # tc filter add dev dummy0 ingress proto ip flower dst_mac aa:bb:cc:dd:ee:ff/00:00:00:00:00:0F action drop
>>>
>>> Addition of filters that does not fit the template would fail:
>>> # tc filter add dev dummy0 ingress proto ip flower dst_mac aa:11:22:33:44:55/00:00:00:FF:00:00 action drop
>>> Error: Mask does not fit the template.
>>> We have an error talking to the kernel, -1
>>> # tc filter add dev dummy0 ingress proto ip flower dst_ip 10.0.0.1 action drop
>>> Error: Mask does not fit the template.
>>> We have an error talking to the kernel, -1
>>>
>>> Additions of filters to chain 22:
>>> # tc filter add dev dummy0 ingress proto ip chain 22 flower dst_ip 10.0.0.1/8 action drop
>>> # tc filter add dev dummy0 ingress proto ip chain 22 flower dst_ip 10.0.0.1 action drop
>>> Error: Mask does not fit the template.
>>> We have an error talking to the kernel, -1
>>> # tc filter add dev dummy0 ingress proto ip chain 22 flower dst_ip 10.0.0.1/24 action drop
>>> Error: Mask does not fit the template.
>>> We have an error talking to the kernel, -1
>>>
>>> Removal of a template from non-empty chain would fail:
>>> # tc chaintemplate del dev dummy0 ingress
>>> Error: The chain is not empty, unable to delete template.
>>> We have an error talking to the kernel, -1
>>
>> Why this restriction? It's a template, so why can't it be removed
>> regardless of whether there are filters?
>
> That means you could start to insert filters that does not match the
> original template. I wanted to avoid it. The chain is utilized in hw for
> the original template, the filter insertion would have to be sanitized
> in driver. With this restriction, drivers can depend on filters always
> be fitting.
>
Then the hardware driver should have that restriction not the core tc code.
next prev parent reply other threads:[~2018-06-28 15:10 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-28 13:08 [patch net-next v2 0/9] net: sched: introduce chain templates support with offloading to mlxsw Jiri Pirko
2018-06-28 13:08 ` [patch net-next v2 1/9] net: sched: push ops lookup bits into tcf_proto_lookup_ops() Jiri Pirko
2018-06-28 13:09 ` [patch net-next v2 2/9] net: sched: introduce chain templates Jiri Pirko
2018-06-28 13:09 ` [patch net-next v2 3/9] net: sched: cls_flower: move key/mask dumping into a separate function Jiri Pirko
2018-06-28 13:09 ` [patch net-next v2 4/9] net: sched: cls_flower: change fl_init_dissector to accept mask and dissector Jiri Pirko
2018-06-28 13:09 ` [patch net-next v2 5/9] net: sched: cls_flower: implement chain templates Jiri Pirko
2018-06-28 13:09 ` [patch net-next v2 6/9] net: sched: cls_flower: propagate chain teplate creation and destruction to drivers Jiri Pirko
2018-06-28 13:09 ` [patch net-next v2 7/9] mlxsw: spectrum: Implement chain template hinting Jiri Pirko
2018-06-28 13:09 ` [patch net-next v2 8/9] selftests: forwarding: move shblock tc support check to a separate helper Jiri Pirko
2018-06-28 13:09 ` [patch net-next v2 9/9] selftests: forwarding: add tests for TC chain templates Jiri Pirko
2018-06-28 13:10 ` [patch iproute2/net-next v2] tc: introduce support for " Jiri Pirko
2018-06-28 13:24 ` [patch net-next v2 0/9] net: sched: introduce chain templates support with offloading to mlxsw Jiri Pirko
2018-06-28 14:18 ` David Ahern
2018-06-28 14:29 ` Jiri Pirko
2018-06-28 15:10 ` David Ahern [this message]
2018-06-28 15:37 ` Jiri Pirko
2018-06-28 15:50 ` David Ahern
2018-06-28 16:08 ` Jiri Pirko
2018-06-28 22:25 ` Cong Wang
2018-06-29 8:39 ` Jiri Pirko
2018-06-29 12:12 ` Jamal Hadi Salim
2018-06-29 12:48 ` Jiri Pirko
2018-06-29 12:54 ` David Ahern
2018-06-29 13:05 ` Jiri Pirko
2018-06-29 17:06 ` Samudrala, Sridhar
2018-06-29 22:18 ` Cong Wang
2018-06-30 10:12 ` Jiri Pirko
2018-07-02 19:33 ` Cong Wang
2018-06-29 13:32 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2018-06-26 7:59 Jiri Pirko
2018-06-27 0:04 ` Cong Wang
2018-06-27 6:05 ` Jiri Pirko
2018-06-27 6:34 ` Samudrala, Sridhar
2018-06-27 7:03 ` Jiri Pirko
2018-06-28 4:48 ` David Miller
2018-06-28 6:25 ` Jiri Pirko
2018-06-28 17:38 ` Cong Wang
2018-06-28 13:13 ` Jamal Hadi Salim
2018-06-28 13:22 ` Jiri Pirko
2018-06-28 13:54 ` Jamal Hadi Salim
2018-06-28 14:17 ` Jiri Pirko
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=1dbc630d-2da3-afbe-18ba-e9dfc893bf04@gmail.com \
--to=dsahern@gmail.com \
--cc=davem@davemloft.net \
--cc=jakub.kicinski@netronome.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=john.hurley@netronome.com \
--cc=mlxsw@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=simon.horman@netronome.com \
--cc=sridhar.samudrala@intel.com \
--cc=xiyou.wangcong@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).