From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Phil Sutter <phil@nwl.cc>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [nft PATCH 0/2] src: Optimize prefix matches on byte-boundaries
Date: Wed, 4 Nov 2020 14:04:31 +0100 [thread overview]
Message-ID: <20201104130431.GA5304@salvia> (raw)
In-Reply-To: <20201027165602.26630-1-phil@nwl.cc>
On Tue, Oct 27, 2020 at 05:56:00PM +0100, Phil Sutter wrote:
> This mini-series optimizes prefix matches to skip the "bitwise"
> expression if they are byte-bound. We can simply reduce "cmp" expression
> length to achieve the same effect.
>
> The first patch adds support for delinearization, this enables correct
> display of the IP address prefix matches added by iptables-nft with my
> (not yet accepted) patch applied.
>
> The second patch enables nft to create such bytecode itself.
Patches LGTM, thanks.
prev parent reply other threads:[~2020-11-04 13:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-27 16:56 [nft PATCH 0/2] src: Optimize prefix matches on byte-boundaries Phil Sutter
2020-10-27 16:56 ` [nft PATCH 1/2] src: Support odd-sized payload matches Phil Sutter
2020-10-27 16:56 ` [nft PATCH 2/2] src: Optimize prefix matches on byte-boundaries Phil Sutter
2020-11-04 13:04 ` Pablo Neira Ayuso [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=20201104130431.GA5304@salvia \
--to=pablo@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=phil@nwl.cc \
/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).