From: "William N." <netfilter@riseup.net>
To: netfilter@vger.kernel.org
Subject: Re: [Thread split] nftables rule optimization - dropping invalid in ingress?
Date: Sat, 27 Apr 2024 19:23:13 -0000 [thread overview]
Message-ID: <20240427192313.4f31c715@localhost> (raw)
In-Reply-To: <20240421174726.7345861d@localhost>
Another test, using only invalid packets, shows the opposite result:
timeout 65s hping3 <host> --flood --xmas
When dropping in ingress:
14455889 packets transmitted
(on <host>) load average: 0.26, 0.30, 0.18
When dropping in prerouting (conntrack 'invalid'):
13794361 packets transmitted
(on <host>) load average: 0.55, 0.29, 0.19
So, after all, dropping in ingress seems faster (5% more packets for
the same time) and x2 less resource intensive.
next prev parent reply other threads:[~2024-04-27 19:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-20 8:48 [Thread split] nftables rule optimization - dropping invalid in ingress? William N.
2024-04-20 18:37 ` William N.
2024-04-20 19:16 ` Kerin Millar
2024-04-21 17:47 ` William N.
2024-04-27 19:23 ` William N. [this message]
2024-04-21 3:45 ` Eric
2024-04-21 5:47 ` Slavko
2024-04-21 17:50 ` 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=20240427192313.4f31c715@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).