From: Patrick McHardy <kaber@trash.net>
To: Harald Welte <laforge@netfilter.org>
Cc: Netfilter Development Mailinglist <netfilter-devel@lists.netfilter.org>
Subject: Re: [PATCH 2.6] connection tracking events
Date: Sat, 16 Oct 2004 15:21:06 +0200 [thread overview]
Message-ID: <41712042.2000505@trash.net> (raw)
In-Reply-To: <20041015175406.GK17516@obroa-skai.de.gnumonks.org>
Hi Harald,
Harald Welte wrote:
>Hi!
>
>Since we decided at the netfilter developer workshop that we want to
>split conntrack events from the rest of ctnetlink, I've now done that
>(and ported it to use percpu allocations). This is needed mostly for
>ct_sync.
>
>
I've already did this in Erlangen. Pablo is currently working with
Krizstian on this patch.
>Totally untested, but seems to compile. Comments welcome.
>
>As it is quite non-intrusive, I think we should consider it for
>post-2.6.9.
>
>
Agreed.
Regards
Patrick
next prev parent reply other threads:[~2004-10-16 13:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-15 17:54 [PATCH 2.6] connection tracking events Harald Welte
2004-10-16 13:21 ` Patrick McHardy [this message]
2004-10-16 15:07 ` Harald Welte
2004-10-16 15:20 ` Patrick McHardy
2004-10-16 15:32 ` Pablo Neira
2004-10-16 18:21 ` Pablo Neira
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=41712042.2000505@trash.net \
--to=kaber@trash.net \
--cc=laforge@netfilter.org \
--cc=netfilter-devel@lists.netfilter.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.