From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: James King <t.james.king@gmail.com>,
Matthew Strait <quadong@users.sourceforge.net>,
Netfilter Development Mailinglist
<netfilter-devel@vger.kernel.org>
Subject: Re: [PATCH RFC] xt_layer7
Date: Thu, 09 Oct 2008 15:59:29 +0200 [thread overview]
Message-ID: <48EE0E41.9010905@trash.net> (raw)
In-Reply-To: <alpine.LNX.1.10.0810081733280.25183@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> On Wednesday 2008-10-08 16:48, James King wrote:
>> Patrick, do you have any objections to these patches (specifically
>> adding NF_CT_EXT_LAYER7), or were you just against Jan's suggestion to
>> make ct_extend to use a linked list for all extensions? If not, would
>> you like me to send a proper patch series?
>>
> It is well understood that a linked list incurs a “rather signifcant”
> runtime hit. Due to simple lack of mass of extensions, we should
> just go for the patch for now.
So you want to keep this externally? Fine by me of course :)
As I stated, I could probably be convinced to add a NF_CT_EXT_LIST
extension where you could dynamically add things since its currently
for free. But it might be too complicated since I think you would
have to duplicate quite a bit of the ct_extend logic.
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2008-10-09 13:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-04 7:22 [PATCH RFC] xt_layer7 James King
2008-10-04 11:58 ` Jan Engelhardt
2008-10-05 13:50 ` Patrick McHardy
2008-10-06 18:57 ` James King
2008-10-06 19:15 ` Jan Engelhardt
2008-10-06 19:48 ` James King
2008-10-08 20:48 ` James King
2008-10-08 21:34 ` Jan Engelhardt
2008-10-09 13:59 ` Patrick McHardy [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=48EE0E41.9010905@trash.net \
--to=kaber@trash.net \
--cc=jengelh@medozas.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=quadong@users.sourceforge.net \
--cc=t.james.king@gmail.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.