From: Pablo Neira Ayuso <pablo@netfilter.org>
To: kaber@trash.net
Cc: netfilter-devel@vger.kernel.org
Subject: [PATCH 0/5] improve ctnetlink event reliability
Date: Fri, 27 Mar 2009 10:38:42 +0100 [thread overview]
Message-ID: <20090327093822.8259.50902.stgit@Decadence> (raw)
Hi Patrick,
This is more like a RFC patch.
The following series are targeted to improve ctnetlink reliability.
I think that the first three patches can be applied safely as they
are merely cleanups. The last two patches may be more controversial,
specifically 4/5 reworks the event caching infrastructure to go over
the conntrack extension infrastructure, thus, leading to more memory
consumption per conntrack. I needed this to add optional reliable
event delivery more cleanly.
Wait for you feedback.
---
Pablo Neira Ayuso (5):
ctnetlink: optional reliable event delivery
conntrack: ecache: move event cache to conntrack extension infrastructure
netfilter: conntrack: don't report events on module removal
netfilter: conntrack: use nf_ct_kill() to destroy conntracks
netfilter: conntrack: remove events flags from userspace exposed file
include/linux/netfilter/nf_conntrack_common.h | 69 --------
include/net/netfilter/nf_conntrack.h | 2
include/net/netfilter/nf_conntrack_core.h | 6 -
include/net/netfilter/nf_conntrack_ecache.h | 169 ++++++++++++++++----
include/net/netfilter/nf_conntrack_extend.h | 2
include/net/netns/conntrack.h | 6 -
net/netfilter/nf_conntrack_core.c | 91 ++++++-----
net/netfilter/nf_conntrack_ecache.c | 214 +++++++++++++++++--------
net/netfilter/nf_conntrack_expect.c | 12 +
net/netfilter/nf_conntrack_ftp.c | 4
net/netfilter/nf_conntrack_netlink.c | 83 ++++++----
net/netfilter/nf_conntrack_pptp.c | 26 ++-
net/netfilter/nf_conntrack_proto_dccp.c | 5 -
net/netfilter/nf_conntrack_proto_sctp.c | 2
net/netfilter/nf_conntrack_proto_tcp.c | 12 +
15 files changed, 435 insertions(+), 268 deletions(-)
--
Signature
next reply other threads:[~2009-03-27 9:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-27 9:38 Pablo Neira Ayuso [this message]
2009-03-27 9:39 ` [PATCH 1/5] netfilter: conntrack: remove events flags from userspace exposed file Pablo Neira Ayuso
2009-03-27 9:39 ` [PATCH 2/5] netfilter: conntrack: use nf_ct_kill() to destroy conntracks Pablo Neira Ayuso
2009-03-27 9:39 ` [PATCH 3/5] netfilter: conntrack: don't report events on module removal Pablo Neira Ayuso
2009-03-27 9:40 ` [PATCH 4/5] conntrack: ecache: move event cache to conntrack extension infrastructure Pablo Neira Ayuso
2009-03-27 9:52 ` Patrick McHardy
2009-03-27 11:37 ` Pablo Neira Ayuso
2009-03-27 11:41 ` Patrick McHardy
2009-03-27 11:57 ` Pablo Neira Ayuso
2009-03-27 11:58 ` Patrick McHardy
2009-03-27 9:40 ` [PATCH 5/5] ctnetlink: optional reliable event delivery Pablo Neira Ayuso
2009-03-27 10:12 ` Patrick McHardy
2009-03-27 12:32 ` Pablo Neira Ayuso
2009-03-27 12:51 ` Patrick McHardy
2009-03-30 11:22 ` 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=20090327093822.8259.50902.stgit@Decadence \
--to=pablo@netfilter.org \
--cc=kaber@trash.net \
--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 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.