From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Phil Sutter <phil@nwl.cc>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [iptables PATCH v2] libxtables: Make sure extensions register in revision order
Date: Wed, 7 Oct 2020 01:59:16 +0200 [thread overview]
Message-ID: <20201006235916.GA2143@salvia> (raw)
In-Reply-To: <20201006120748.22006-1-phil@nwl.cc>
On Tue, Oct 06, 2020 at 02:07:48PM +0200, Phil Sutter wrote:
> Insert extensions into pending lists in ordered fashion: Group by
> extension name (and, for matches, family) and order groups by descending
> revision number.
>
> This allows to simplify the later full registration considerably. Since
> that involves kernel compatibility checks, the extra cycles here pay off
> eventually.
LGTM.
next prev parent reply other threads:[~2020-10-06 23:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 22:53 [iptables PATCH 0/3] libxtables: Fix for pointless socket() calls Phil Sutter
2020-09-22 22:53 ` [iptables PATCH 1/3] libxtables: Make sure extensions register in revision order Phil Sutter
2020-10-03 11:17 ` Pablo Neira Ayuso
2020-10-04 14:53 ` Phil Sutter
2020-10-05 22:42 ` Pablo Neira Ayuso
2020-10-06 9:27 ` Phil Sutter
2020-10-06 9:50 ` Pablo Neira Ayuso
2020-10-06 10:13 ` Phil Sutter
2020-10-06 10:48 ` Pablo Neira Ayuso
2020-10-06 12:07 ` [iptables PATCH v2] " Phil Sutter
2020-10-06 23:59 ` Pablo Neira Ayuso [this message]
2020-09-22 22:53 ` [iptables PATCH 2/3] libxtables: Simplify pending extension registration Phil Sutter
2020-10-05 23:08 ` Pablo Neira Ayuso
2020-09-22 22:53 ` [iptables PATCH 3/3] libxtables: Register multiple extensions in ascending order Phil Sutter
2020-10-05 23:41 ` Pablo Neira Ayuso
2020-10-06 9:29 ` Phil Sutter
2020-09-23 11:45 ` [iptables PATCH 0/3] libxtables: Fix for pointless socket() calls Pablo Neira Ayuso
2020-09-23 14:30 ` Phil Sutter
2020-10-07 0:02 ` Pablo Neira Ayuso
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=20201006235916.GA2143@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 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.