From: "William N." <netfilter@riseup.net>
To: netfilter@vger.kernel.org
Subject: Re: nftables rule optimization - evaluating efficiency
Date: Thu, 11 Jul 2024 19:15:12 -0000 [thread overview]
Message-ID: <20240711191512.084c060a@localhost> (raw)
In-Reply-To: <20240710213901.GB550@breakpoint.cc>
On Wed, 10 Jul 2024 23:39:01 +0200 Florian Westphal wrote:
> In general, its best to compact the ruleset as much as possible
> and use sets/maps/vmaps wherever possible.
That's what I suspected too.
next prev parent reply other threads:[~2024-07-11 19:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 19:03 nftables rule optimization - evaluating efficiency William N.
2024-07-03 9:37 ` Reindl Harald
2024-07-03 10:44 ` William N.
2024-07-10 18:34 ` William N.
2024-07-10 21:27 ` Kerin Millar
2024-07-10 21:39 ` Florian Westphal
2024-07-11 19:15 ` William N. [this message]
2024-07-11 19:14 ` William N.
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=20240711191512.084c060a@localhost \
--to=netfilter@riseup.net \
--cc=netfilter@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).