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/5] netfilter: conntrack: shrink size of netns_ct
Date: Tue, 13 Apr 2021 13:13:53 +0200 [thread overview]
Message-ID: <20210413111353.GA3934@salvia> (raw)
In-Reply-To: <20210412195544.417-1-fw@strlen.de>
On Mon, Apr 12, 2021 at 09:55:39PM +0200, Florian Westphal wrote:
> v2: fix linker error when PROCFS=n. This only affects patch 4/5, no
> other changes.
>
> This reduces size of the netns_ct structure, which itself is embedded
> in struct net.
>
> First two patches move two helper related settings to net_generic,
> these are only accessed when a new connection is added.
>
> Patches 3 and 4 move the ct and expect counter to net_generic too.
> While these are used from packet path, they are not accessed when
> conntack finds an existing entry.
>
> This also makes netns_ct a read-mostly structure, at this time each
> newly accepted conntrack dirties the first netns_ct cacheline for other
> cpus.
>
> Last patch converts a few sysctls to u8. Most conntrack sysctls are
> timeouts, so these need to be kept as ints.
Series applied, thanks.
prev parent reply other threads:[~2021-04-13 11:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-12 19:55 [PATCH nf-next v2 0/5] netfilter: conntrack: shrink size of netns_ct Florian Westphal
2021-04-12 19:55 ` [PATCH nf-next v2 1/5] netfilter: conntrack: move autoassign warning member to net_generic data Florian Westphal
2021-04-12 19:55 ` [PATCH nf-next v2 2/5] netfilter: conntrack: move autoassign_helper sysctl " Florian Westphal
2021-04-12 19:55 ` [PATCH nf-next v2 3/5] netfilter: conntrack: move expect counter " Florian Westphal
2021-04-12 19:55 ` [PATCH nf-next v2 4/5] netfilter: conntrack: move ct " Florian Westphal
2021-04-12 19:55 ` [PATCH nf-next v2 5/5] netfilter: conntrack: convert sysctls to u8 Florian Westphal
2021-04-13 11:13 ` 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=20210413111353.GA3934@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).