From: Patrick McHardy <kaber@trash.net>
To: Jiri Olsa <jolsa@redhat.com>
Cc: Tim Waugh <twaugh@redhat.com>, netfilter-devel@vger.kernel.org
Subject: Re: [RFC,PATCH] netfilter: SNMP conntrack module
Date: Sat, 15 Jan 2011 17:15:00 +0100 [thread overview]
Message-ID: <4D31C804.5090304@trash.net> (raw)
In-Reply-To: <20110114201805.GC4546@jolsa.brq.redhat.com>
Am 14.01.2011 21:18, schrieb Jiri Olsa:
> hi,
>
> attached patch adds SNMP conntrack module to the netfilter.
>
> I refer to the following conversation:
> http://marc.info/?l=netfilter-devel&m=125992205006600&w=2
>
> Patrick McHardy wrote:
>> The best solution would be to add generic broadcast tracking, the
>> use of expectations for this is a bit of abuse.
>
>> The second best choice I guess would be to move the help() function
>> to a shared module and generalize it so it can be used for both.
>
> The patch tries to implement the "second best choice".
>
> In case the 'second best choice' is not good enough anyway,
> could you please outline the first one in more detail..?
Adding full broadcast tracking is non-trivial, so this is good
enough for now.
> Also the patch is not adding the "help" function to the
> shared module, since I'm not sure where to put it. If the
> idea of the patch would be acceptable, could you please
> suggest the shared module for the 'help' function?
How about adding a nf_conntrack_broadcast.c or something
like that and keep the common code there? The help function
and the expect policy (probably not really worth it) could
be moved to that file.
> --- /dev/null
> +++ b/net/netfilter/nf_conntrack_snmp.c
Besides Jan comments, the patch looks fine to me.
next prev parent reply other threads:[~2011-01-15 16:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-14 20:18 [RFC,PATCH] netfilter: SNMP conntrack module Jiri Olsa
2011-01-14 21:18 ` Jan Engelhardt
2011-01-15 16:15 ` Patrick McHardy [this message]
2011-01-17 9:45 ` [PATCH] netfilter: nf_conntrack snmp helper Jiri Olsa
2011-01-18 13:45 ` Patrick McHardy
2011-01-18 16:37 ` [PATCHv2] " Jiri Olsa
2011-01-18 17:14 ` Patrick McHardy
2011-01-18 17:21 ` Jiri Olsa
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=4D31C804.5090304@trash.net \
--to=kaber@trash.net \
--cc=jolsa@redhat.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=twaugh@redhat.com \
/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.