From: Xin Long <lucien.xin@gmail.com>
To: network dev <netdev@vger.kernel.org>
Cc: davem@davemloft.net, kuba@kernel.org,
Jamal Hadi Salim <jhs@mojatatu.com>,
Cong Wang <xiyou.wangcong@gmail.com>,
Jiri Pirko <jiri@resnulli.us>,
Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>,
Davide Caratti <dcaratti@redhat.com>, Oz Shlomo <ozsh@nvidia.com>,
Paul Blakey <paulb@nvidia.com>,
Ilya Maximets <i.maximets@ovn.org>
Subject: [PATCH net-next 0/2] net: sched: add helper support in act_ct for ovs offloading
Date: Fri, 23 Sep 2022 11:28:25 -0400 [thread overview]
Message-ID: <cover.1663946157.git.lucien.xin@gmail.com> (raw)
Ilya reported an issue that FTP traffic would be broken when the OVS flow
with ct(commit,alg=ftp) was installed in the OVS kernel module, which was
caused by that TC didn't support the ftp helper offloaded from OVS.
This patchset is to add the helper support for ovs offloading. Note that
the 1st patch is fixing a memleak issue, and also making the 2nd patch
easier to write for the feature support.
Xin Long (2):
net: sched: fix the err path of tcf_ct_init in act_ct
net: sched: add helper support in act_ct
include/net/tc_act/tc_ct.h | 1 +
include/uapi/linux/tc_act/tc_ct.h | 3 +
net/sched/act_ct.c | 193 +++++++++++++++++++++++++++---
3 files changed, 182 insertions(+), 15 deletions(-)
--
2.31.1
next reply other threads:[~2022-09-23 15:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 15:28 Xin Long [this message]
2022-09-23 15:28 ` [PATCH net-next 1/2] net: sched: fix the err path of tcf_ct_init in act_ct Xin Long
2022-09-27 12:43 ` Paolo Abeni
2022-09-27 14:45 ` Xin Long
2022-09-27 16:29 ` Paolo Abeni
2022-09-23 15:28 ` [PATCH net-next 2/2] net: sched: add helper support " Xin Long
2022-09-27 10:29 ` Paolo Abeni
2022-09-27 15:04 ` Xin Long
2022-10-04 12:33 ` Ilya Maximets
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=cover.1663946157.git.lucien.xin@gmail.com \
--to=lucien.xin@gmail.com \
--cc=davem@davemloft.net \
--cc=dcaratti@redhat.com \
--cc=i.maximets@ovn.org \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=ozsh@nvidia.com \
--cc=paulb@nvidia.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).