From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
linux-rt-devel@lists.linux.dev,
Jozsef Kadlecsik <kadlec@netfilter.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH net-next v2 0/3] Replace xt_recseq with u64_stats.
Date: Mon, 24 Mar 2025 17:29:23 +0100 [thread overview]
Message-ID: <20250324162923.O308UeBw@linutronix.de> (raw)
In-Reply-To: <Z90-Q3zyEHDWPBNr@calendula>
On 2025-03-21 11:24:03 [+0100], Pablo Neira Ayuso wrote:
> Hi Sebastian,
Hi Pablo,
> I have been discussing this with Florian, our proposal:
>
> 1. Make ipatbles legacy depend on !PREEMPT_RT which effectively
> disabled iptables classic for RT.
>
> This should be ok, iptables-nft should work for RT.
>
> 2. make iptables-legacy user-selectable.
>
> these two are relatively simple.
Okay. Let me try that.
> If this does not make you happy, it should be possible to take your
> patches plus hide synchronize_rcu() latency behind deferred free
> (call_rcu+workqueue).
I will try the suggested above and then will see who complains. But I
think it should be doable to roll with nft only for future releases.
> Thanks.
Sebastian
next prev parent reply other threads:[~2025-03-24 16:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 13:31 [PATCH net-next v2 0/3] Replace xt_recseq with u64_stats Sebastian Andrzej Siewior
2025-02-21 13:31 ` [PATCH net-next v2 1/3] netfilter: Make xt_table::private RCU protected Sebastian Andrzej Siewior
2025-02-21 13:31 ` [PATCH net-next v2 2/3] netfilter: Split the xt_counters type between kernel and user Sebastian Andrzej Siewior
2025-02-21 13:31 ` [PATCH net-next v2 3/3] netfilter: Use u64_stats for counters in xt_counters_k Sebastian Andrzej Siewior
2025-03-07 16:57 ` [PATCH net-next v2 0/3] Replace xt_recseq with u64_stats Sebastian Andrzej Siewior
2025-03-12 23:16 ` Pablo Neira Ayuso
2025-03-13 8:34 ` Sebastian Andrzej Siewior
2025-03-20 12:41 ` Pablo Neira Ayuso
2025-03-21 10:24 ` Pablo Neira Ayuso
2025-03-24 16:29 ` Sebastian Andrzej Siewior [this message]
2025-03-24 17:47 ` Florian Westphal
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=20250324162923.O308UeBw@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=coreteam@netfilter.org \
--cc=kadlec@netfilter.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=tglx@linutronix.de \
/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).