From: wenxu <wenxu@ucloud.cn>
To: Jakub Kicinski <kuba@kernel.org>,
Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
Cc: Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: [resend] Solution for the problem conntrack in tc subsystem
Date: Thu, 29 Oct 2020 10:22:04 +0800 [thread overview]
Message-ID: <435e4756-f36a-f0f5-0ac5-45bd5cacaff2@ucloud.cn> (raw)
In-Reply-To: <7821f3ae-0e71-0d8b-5ef9-81da69ac29dc@ucloud.cn>
Hi,
Currently kernel tc subsystem can do conntrack things in cat_ct. But there is a problem need
to fix. For several fragment packets handle in act_ct. The tcf_ct_handle_fragments will defrag
the packets to a big one. But the after action will redirect mirror to a device which maybe lead
the reassembly big packet over the mtu of target device.
The proposal "net/sched: act_mirred: fix fragment the packet after defrag in act_ct"
http://patchwork.ozlabs.org/project/netdev/patch/1593485646-14989-1-git-send-email-wenxu@ucloud.cn/
is not been accepted.
another proposal "net/sched: add act_ct_output support"
http://patchwork.ozlabs.org/project/netdev/patch/1598335663-26503-1-git-send-email-wenxu@ucloud.cn/
is also not a good solution. There are some duplicate codes for this and act_mirred.
Something other proposal like add the act_fragment also can't be work. The fragment will make
The big packet to several ones and can't be handle in the tc pipe. And also this is not friendly for
user to explicitly add action for fragment.
Only do gso for the reassembly big packet is also can't fix all the case such for icmp packet.
So there are some proper solution for this problem. In the Internet we can't avoid the fragment packets.
BR
wenxu
next parent reply other threads:[~2020-10-29 2:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7821f3ae-0e71-0d8b-5ef9-81da69ac29dc@ucloud.cn>
2020-10-29 2:22 ` wenxu [this message]
2020-10-29 22:59 ` [resend] Solution for the problem conntrack in tc subsystem Marcelo Ricardo Leitner
2020-10-30 12:19 ` Marcelo Ricardo Leitner
2020-11-02 6:08 ` wenxu
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=435e4756-f36a-f0f5-0ac5-45bd5cacaff2@ucloud.cn \
--to=wenxu@ucloud.cn \
--cc=kuba@kernel.org \
--cc=marcelo.leitner@gmail.com \
--cc=netdev@vger.kernel.org \
/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).