From: Florian Westphal <fw@strlen.de>
To: <netfilter-devel@vger.kernel.org>
Subject: [PATCH nf-next 0/3] netfilter: conntrack: prepare for hashtable merge, take 1
Date: Mon, 18 Apr 2016 16:16:58 +0200 [thread overview]
Message-ID: <1460989021-10780-1-git-send-email-fw@strlen.de> (raw)
This small series prepares for upcoming merge of the per-namespace hash tables
into a single table (or rater, three tables
-- conntrack hash, expect hash and nat bysrc hash).
Arguments for merging it:
- We stop wasting (assuming default size) 250k backing store per namespace
- net namespace is just another part of the connection id, much like
ip addresses or conntrack zones -- no need to treat it specially
- allows to get rid of the per-netns conntrack slab as well
These patches are first preparations.
We replace per-netns conntrack has generation seqcount by single one.
While at it, this replaces the method used to obtain the hash seed
by the (nowadays) more common get_random_once().
next reply other threads:[~2016-04-18 14:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-18 14:16 Florian Westphal [this message]
2016-04-18 14:16 ` [PATCH nf-next 1/3] netfilter: conntrack: move generation seqcnt out of netns_ct Florian Westphal
2016-04-18 14:17 ` [PATCH nf-next 2/3] netfilter: conntrack: use get_random_once for nat and expectations Florian Westphal
2016-04-24 14:09 ` Pablo Neira Ayuso
2016-04-24 15:16 ` Florian Westphal
2016-04-24 17:50 ` Hannes Frederic Sowa
2016-04-24 18:59 ` Hannes Frederic Sowa
2016-04-18 14:17 ` [PATCH nf-next 3/3] netfilter: conntrack: use get_random_once for conntrack hash seed Florian Westphal
2016-04-25 12:26 ` [PATCH nf-next 0/3] netfilter: conntrack: prepare for hashtable merge, take 1 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=1460989021-10780-1-git-send-email-fw@strlen.de \
--to=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).