From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Julius Bairaktaris <julius@bairaktaris.de>
Cc: netfilter-devel@vger.kernel.org, kadlec@netfilter.org,
fw@strlen.de, coreteam@netfilter.org, netdev@vger.kernel.org,
geldot@protonmail.com, shuah@kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH nf-next v2 0/4] netfilter: offload a TCP flow whose reply is never seen
Date: Sun, 18 Oct 2026 04:00:15 +0200 [thread overview]
Message-ID: <atQoL7WUM3BvDwbI@chamomile> (raw)
In-Reply-To: <20261018015434.3326758-1-julius@bairaktaris.de>
On Sun, Oct 18, 2026 at 03:54:34AM +0200, Julius Bairaktaris wrote:
> On Sun, Oct 18, 2026 at 03:42:58AM +0200, Pablo Neira Ayuso wrote:
> > This series are a no-go in this approach.
>
> Understood, I drop it.
>
> > Please, given we are discussing one series of you quite recently...
> > let's handle one thing at a time.
>
> Agreed, the fdb series first.
>
> Some context on why there are so many: they all come from the OpenWrt
> PR that adds flowtable offload for the Qualcomm IPQ807x PPE:
>
> https://github.com/openwrt/openwrt/pull/24806
>
> That PR carries the kernel changes it needs as patches. I am sending
> them upstream so that OpenWrt can carry backports instead of local
> patches.
>
> I know the rule that there must be an in-tree user. The PPE driver is
> not upstream, so I only send changes that stand on their own: fixes to
> the software path, or features that existing drivers like airoha and
> mtk use.
Thanks for the context. As said, let's go one by one after each
issue/scenario. We will eventually get to all of your described
scenarios.
next prev parent reply other threads:[~2026-10-18 2:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-04 17:16 [PATCH nf-next v2 0/4] netfilter: offload a TCP flow whose reply is never seen Julius Bairaktaris
2026-10-04 17:16 ` [PATCH nf-next v2 1/4] netfilter: conntrack: pick up a TCP flow whose SYN was never answered Julius Bairaktaris
2026-10-18 1:36 ` Pablo Neira Ayuso
2026-10-04 17:16 ` [PATCH nf-next v2 2/4] netfilter: flowtable: promote a flow offloaded in one direction only Julius Bairaktaris
2026-10-04 17:16 ` [PATCH nf-next v2 3/4] netfilter: nft_flow_offload: offload a TCP flow that has no reply Julius Bairaktaris
2026-10-04 17:16 ` [PATCH nf-next v2 4/4] selftests: netfilter: cover a TCP flow whose reply is never seen Julius Bairaktaris
2026-10-17 10:37 ` [PATCH nf-next v2 0/4] netfilter: offload " Julius Bairaktaris
2026-10-18 1:42 ` Pablo Neira Ayuso
2026-10-18 1:54 ` Julius Bairaktaris
2026-10-18 2:00 ` Pablo Neira Ayuso [this message]
2026-10-18 2:02 ` Julius Bairaktaris
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=atQoL7WUM3BvDwbI@chamomile \
--to=pablo@netfilter.org \
--cc=coreteam@netfilter.org \
--cc=fw@strlen.de \
--cc=geldot@protonmail.com \
--cc=julius@bairaktaris.de \
--cc=kadlec@netfilter.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=shuah@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 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.