From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Florian Westphal <fw@strlen.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH nf-next v2 0/7] netfilter: remove pcpu dying list
Date: Thu, 3 Mar 2022 00:26:43 +0100 [thread overview]
Message-ID: <Yh/9M0nBZWiAH8T4@salvia> (raw)
In-Reply-To: <20220224164446.23208-1-fw@strlen.de>
On Thu, Feb 24, 2022 at 05:44:39PM +0100, Florian Westphal wrote:
> v2: fix EXPORT_SYMBOL_GPL related build failure in patch 6.
> No other changes.
>
> This is part 1 of a series that aims to remove both the unconfirmed
> and dying lists.
>
> This moves the dying list into the ecache infrastructure.
> Entries are placed on this list only if the delivery of the destroy
> event has failed (which implies that at least one userspace listener
> did request redelivery).
>
> The percpu dying list is removed in the last patch as it has no
> functionality anymore. This avoids the extra spinlock for conntrack
> removal.
Applied, thanks
prev parent reply other threads:[~2022-03-03 0:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 16:44 [PATCH nf-next v2 0/7] netfilter: remove pcpu dying list Florian Westphal
2022-02-24 16:44 ` [PATCH nf-next v2 1/7] nfnetlink: handle already-released nl socket Florian Westphal
2022-02-24 16:44 ` [PATCH nf-next v2 2/7] netfilter: ctnetlink: make ecache event cb global again Florian Westphal
2022-02-24 16:44 ` [PATCH nf-next v2 3/7] netfilter: ecache: move to separate structure Florian Westphal
2022-02-24 16:44 ` [PATCH nf-next v2 4/7] netfilter: ecache: use dedicated list for event redelivery Florian Westphal
2022-02-24 16:44 ` [PATCH nf-next v2 5/7] netfilter: conntrack: split inner loop of list dumping to own function Florian Westphal
2022-02-24 16:44 ` [PATCH nf-next v2 6/7] netfilter: conntrack: include ecache dying list in dumps Florian Westphal
2022-02-24 16:44 ` [PATCH nf-next v2 7/7] netfilter: conntrack: remove the percpu dying list Florian Westphal
2022-03-02 23:26 ` 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=Yh/9M0nBZWiAH8T4@salvia \
--to=pablo@netfilter.org \
--cc=fw@strlen.de \
--cc=netfilter-devel@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).