[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAM_iQpVf-iPRZNipWo9VJrK5H5A44ti1zbXyfVCtd_mQeJZQWw@mail.gmail.com>
Date: Fri, 14 Sep 2018 14:09:48 -0700
From: Cong Wang <xiyou.wangcong@...il.com>
To: Jiri Pirko <jiri@...nulli.us>
Cc: amritha.nambiar@...el.com,
Linux Kernel Network Developers <netdev@...r.kernel.org>,
David Miller <davem@...emloft.net>,
Alexander Duyck <alexander.h.duyck@...el.com>,
Jakub Kicinski <jakub.kicinski@...ronome.com>,
sridhar.samudrala@...el.com, Jamal Hadi Salim <jhs@...atatu.com>,
Jesse Brandeburg <jesse.brandeburg@...el.com>
Subject: Re: [net-next,RFC PATCH] Introduce TC Range classifier
On Fri, Sep 14, 2018 at 2:53 AM Jiri Pirko <jiri@...nulli.us> wrote:
>
> Thu, Sep 13, 2018 at 10:52:01PM CEST, amritha.nambiar@...el.com wrote:
> >This patch introduces a TC range classifier to support filtering based
> >on ranges. Only port-range filters are supported currently. This can
> >be combined with flower classifier to support filters that are a
> >combination of port-ranges and other parameters based on existing
> >fields supported by cls_flower. The 'goto chain' action can be used to
> >combine the flower and range filter.
> >The filter precedence is decided based on the 'prio' value.
>
> For example Spectrum ASIC supports mask-based and range-based matching
> in a single TCAM rule. No chains needed. Also, I don't really understand
> why is this a separate cls. I believe that this functionality should be
> put as an extension of existing cls_flower.
Exactly. u32 filters support range matching too with proper masks.
Powered by blists - more mailing lists