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: Wed, 10 Jul 2024 18:34:51 -0000	[thread overview]
Message-ID: <20240710183451.0f193976@localhost> (raw)
In-Reply-To: <20240702190318.618a3933@localhost>

On Tue, 2 Jul 2024 19:03:18 -0000 William N. wrote:

> [...]
> Also, it is not clear what is the actual "load" of different
> instructions in terms of CPU cycles and memory, i.e. one instruction
> may look as "one" but may actually cost more than another 2, right?
> 
> What is the proper way to evaluate and optimize rule efficiency?

Are those difficult or somehow inappropriate questions?
Or is there a better place to ask?

  parent reply	other threads:[~2024-07-10 18:43 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. [this message]
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.

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=20240710183451.0f193976@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.