All of lore.kernel.org
 help / color / mirror / Atom feed
From: "William N." <netfilter@riseup.net>
To: netfilter@vger.kernel.org
Subject: Re: nftables rule optimization - evaluating efficiency
Date: Thu, 11 Jul 2024 19:14:43 -0000	[thread overview]
Message-ID: <20240711191443.26d294df@localhost> (raw)
In-Reply-To: <1c12afa3-40fd-48df-9076-92277570ef3b@app.fastmail.com>

On Wed, 10 Jul 2024 22:27:02 +0100 Kerin Millar wrote:

> Indeed. It cannot be presumed that all instructions are equal in expense.

I suppose it may actually be even more complicated if different CPU
architectures (all capable of running nft) are considered in a
comparison. So, for simplicity, I was hoping to be able to evaluate
things at least on a single architecture.

> It is a pity

Well, I guess I have touched a subject not interesting for many (hence
not documented).

      parent reply	other threads:[~2024-07-11 19:14 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.
2024-07-11 19:14     ` William N. [this message]

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=20240711191443.26d294df@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 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.