From: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>
To: Jakub Kicinski <jakub.kicinski@netronome.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
nirranjan@chelsio.com, vishal@chelsio.com, dt@chelsio.com
Subject: Re: [PATCH net-next v2 2/2] cxgb4: add TC-MATCHALL classifier ingress offload
Date: Fri, 15 Nov 2019 01:14:41 +0530 [thread overview]
Message-ID: <20191114194435.GA12678@chelsio.com> (raw)
In-Reply-To: <20191114102037.6df3aa23@cakuba.netronome.com>
On Thursday, November 11/14/19, 2019 at 10:20:37 -0800, Jakub Kicinski wrote:
> On Thu, 14 Nov 2019 21:04:05 +0530, Rahul Lakkireddy wrote:
> > Add TC-MATCHALL classifier ingress offload support. The same actions
> > supported by existing TC-FLOWER offload can be applied to all incoming
> > traffic on the underlying interface.
> >
> > Only 1 ingress matchall rule can be active at a time on the underlying
> > interface.
> >
> > Signed-off-by: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>
> > ---
> > v2:
> > - Removed logic to fetch free index from end of TCAM. Must maintain
> > same ordering as in kernel.
>
> The ordering in the kernel is by filter priority/pref. Not the order of
> addition (which AFAIK you're intending to preserve here?).
>
> Since you're only offloading the policer presumably you want to limit
> the port speed. The simplest way to make sure the rule ordering is right
> is to only accept the policer as the highest prio rule. I believe OvS
> installs it always with prio 1.
Ok, I've misunderstood your comment earlier. Will add a check in patch 1
to reject policer, if prio is not 1.
Thanks,
Rahul
prev parent reply other threads:[~2019-11-14 19:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-14 15:34 [PATCH net-next v2 0/2] cxgb4: add TC-MATCHALL classifier offload Rahul Lakkireddy
2019-11-14 15:34 ` [PATCH net-next v2 1/2] cxgb4: add TC-MATCHALL classifier egress offload Rahul Lakkireddy
2019-11-14 15:34 ` [PATCH net-next v2 2/2] cxgb4: add TC-MATCHALL classifier ingress offload Rahul Lakkireddy
2019-11-14 18:20 ` Jakub Kicinski
2019-11-14 19:44 ` Rahul Lakkireddy [this message]
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=20191114194435.GA12678@chelsio.com \
--to=rahul.lakkireddy@chelsio.com \
--cc=davem@davemloft.net \
--cc=dt@chelsio.com \
--cc=jakub.kicinski@netronome.com \
--cc=netdev@vger.kernel.org \
--cc=nirranjan@chelsio.com \
--cc=vishal@chelsio.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).