All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Harald Welte <laforge@netfilter.org>
Cc: Netfilter Development Mailinglist
	<netfilter-devel@lists.netfilter.org>,
	Pablo Neira <pablo@eurodev.net>,
	KOVACS Krisztian <hidden@balabit.hu>
Subject: Re: [PATCH] Introducing the Change API
Date: Fri, 17 Dec 2004 06:28:55 +0100	[thread overview]
Message-ID: <41C26E97.8000805@trash.net> (raw)
In-Reply-To: <20041216124049.GF10165@sunbeam.de.gnumonks.org>

Harald Welte wrote:

>On Sun, Dec 05, 2004 at 09:23:53PM +0100, Patrick McHardy wrote:
>
>  
>
>>I think that depends on what we want to do with ip_conntrack once
>>nf_conntrack is merged. Since I really don't feel like keeping
>>three codebases in sync (ip_conntrack 2.4 + 2.6 and nf_conntrack),
>>I would prefer to remove it. If we do this, it doesn't make much
>>sense to add further features to it. But I'm not sure what Harald's
>>and Krisztian's plans are for ct_sync, so they might disagree with me.
>>    
>>
>
>I think we should move to nf_conntrack ASAP.  All new
>code/features/API's should be developed on top of nf_conntrack.  We
>really should put ip_conntrack into a maintainance-only mode once
>nf_conntrack becomes mainline.
>  
>
Agreed.

>Actually I only want to do some nf_conntrack vs. ip_conntrack
>benchmarking, which I never got aroun doing up to now :(  With a little
>luck, I can do this over the weekend.  If the results are acceptable,
>nf_conntrack will be submitted maybe as soon as 2.6.11. 
>  
>
I would like to give it some cleanup first. Since it doesn't need to
deal with ipchains compatibility there is a lot possible cleanup.
I will probably do this in the next couple of weeks.

Regards
Patrick

  parent reply	other threads:[~2004-12-17  5:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-04 22:15 [PATCH] Introducing the Change API Pablo Neira
2004-12-05 20:23 ` Patrick McHardy
2004-12-16 12:40   ` Harald Welte
2004-12-16 12:53     ` KOVACS Krisztian
2004-12-16 15:34     ` Pablo Neira
2004-12-17  5:28     ` Patrick McHardy [this message]
2004-12-17  8:08       ` Harald Welte
2004-12-17 17:26         ` Patrick McHardy

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=41C26E97.8000805@trash.net \
    --to=kaber@trash.net \
    --cc=hidden@balabit.hu \
    --cc=laforge@netfilter.org \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=pablo@eurodev.net \
    /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.