From: Jiri Pirko <jiri@resnulli.us>
To: Amritha Nambiar <amritha.nambiar@intel.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
alexander.h.duyck@intel.com, jakub.kicinski@netronome.com,
sridhar.samudrala@intel.com, jhs@mojatatu.com,
jesse.brandeburg@intel.com, xiyou.wangcong@gmail.com
Subject: Re: [net-next,RFC PATCH] Introduce TC Range classifier
Date: Fri, 14 Sep 2018 11:49:32 +0200 [thread overview]
Message-ID: <20180914094932.GK25110@nanopsycho> (raw)
In-Reply-To: <153687160312.43503.11156697286063840163.stgit@anamhost.jf.intel.com>
Thu, Sep 13, 2018 at 10:52:01PM CEST, amritha.nambiar@intel.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.
next prev parent reply other threads:[~2018-09-14 15:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-13 20:52 [net-next,RFC PATCH] Introduce TC Range classifier Amritha Nambiar
2018-09-13 20:52 ` [net-next, RFC PATCH] net: sched: cls_range: Introduce " Amritha Nambiar
2018-09-14 9:58 ` Jiri Pirko
2018-09-15 1:31 ` Nambiar, Amritha
2018-09-14 21:06 ` Cong Wang
2018-09-14 9:49 ` Jiri Pirko [this message]
2018-09-14 21:09 ` [net-next,RFC PATCH] Introduce TC " Cong Wang
2018-09-15 1:29 ` Nambiar, Amritha
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=20180914094932.GK25110@nanopsycho \
--to=jiri@resnulli.us \
--cc=alexander.h.duyck@intel.com \
--cc=amritha.nambiar@intel.com \
--cc=davem@davemloft.net \
--cc=jakub.kicinski@netronome.com \
--cc=jesse.brandeburg@intel.com \
--cc=jhs@mojatatu.com \
--cc=netdev@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.