From: Edward Cree <ecree@solarflare.com>
To: Paul Blakey <paulb@mellanox.com>,
Saeed Mahameed <saeedm@mellanox.com>,
Oz Shlomo <ozsh@mellanox.com>,
Jakub Kicinski <jakub.kicinski@netronome.com>,
Vlad Buslov <vladbu@mellanox.com>,
"David Miller" <davem@davemloft.net>, <netdev@vger.kernel.org>,
Jiri Pirko <jiri@mellanox.com>, Roi Dayan <roid@mellanox.com>
Subject: Re: [PATCH net-next 0/3] net/sched: act_ct: Add support for specifying tuple offload policy
Date: Thu, 14 May 2020 15:04:02 +0100 [thread overview]
Message-ID: <3d780eae-3d53-77bb-c3b9-775bf50477bf@solarflare.com> (raw)
In-Reply-To: <1589464110-7571-1-git-send-email-paulb@mellanox.com>
On 14/05/2020 14:48, Paul Blakey wrote:
> To avoid conflicting policies, the policy is applied per zone on the first
> act ct instance for that zone, and must be repeated in all further act ct
> instances of the same zone.
Is the scope of this the entire zone, or just offload of that zone to a
specific device?
Either way, the need to repeat the policy on every tc command suggests
that there really ought to instead be a separate API for configuring
conntrack offload policy, either per zone or per (zone, device) pair,
as appropriate.
-ed
next prev parent reply other threads:[~2020-05-14 14:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 13:48 [PATCH net-next 0/3] net/sched: act_ct: Add support for specifying tuple offload policy Paul Blakey
2020-05-14 13:48 ` [PATCH net-next 1/3] netfilter: flowtable: Control flow offload timeout interval Paul Blakey
2020-05-14 13:48 ` [PATCH net-next 2/3] net/sched: act_ct: Add policy_pkts tuple offload control policy Paul Blakey
2020-05-14 13:48 ` [PATCH net-next 3/3] net/sched: act_ct: Add policy_timeout " Paul Blakey
2020-05-14 14:04 ` Edward Cree [this message]
2020-05-14 14:49 ` [PATCH net-next 0/3] net/sched: act_ct: Add support for specifying tuple offload policy Jiri Pirko
2020-05-14 15:28 ` Edward Cree
2020-05-18 16:17 ` Paul Blakey
2020-05-18 16:48 ` Edward Cree
2020-05-18 17:25 ` Jiri Pirko
2020-05-18 18:02 ` Edward Cree
2020-05-26 9:25 ` Paul Blakey
2020-05-26 16:17 ` Edward Cree
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=3d780eae-3d53-77bb-c3b9-775bf50477bf@solarflare.com \
--to=ecree@solarflare.com \
--cc=davem@davemloft.net \
--cc=jakub.kicinski@netronome.com \
--cc=jiri@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=ozsh@mellanox.com \
--cc=paulb@mellanox.com \
--cc=roid@mellanox.com \
--cc=saeedm@mellanox.com \
--cc=vladbu@mellanox.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).