All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@lists.netfilter.org, Eric Leblond <eric@inl.fr>
Subject: Re: [PATCH] Unconditionaly push mark to conntrack structure
Date: Thu, 08 Jun 2006 09:25:22 +0200	[thread overview]
Message-ID: <4487D0E2.4030705@trash.net> (raw)
In-Reply-To: <44856875.2020108@netfilter.org>

Pablo Neira Ayuso wrote:
> Patrick McHardy wrote:
> 
>> Pablo Neira Ayuso wrote:
>>
>>> To be frank, I can't see how the timer can be useful from userspace. I
>>> think that we should remove it.
>>
>>
>>
>> Don't you need it for synchronization? One example where it could be
>> useful is to implement different timeout strategies (for example
>> something like pf's adaptive timeouts) in userspace.
> 
> 
> But these adaptive timeouts could be implemented in kernelspace.

Thats not a good argument .. by that logic we wouldn't need ctnetlink
at all :)

> Unfortunately, ctnetlink is not doing any sequence tracking of the
> events at the moment :( and we have to. Here my old PIII 866MHz with a
> 100Mbits network card starts dropping events when it reaches ~300
> simultaneos short TCP connections (2 seconds) with netperf. I'm going to
> cook a patch for this.

That seems to be pretty poor performance - by sequence tracking you
mean TCP state updates? Is that poor performance with or without
them?

  reply	other threads:[~2006-06-08  7:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-19  8:45 [PATCH] Unconditionaly push mark to conntrack structure Eric Leblond
2006-05-30 23:43 ` Patrick McHardy
2006-05-30 23:55   ` Patrick McHardy
2006-05-31  0:26     ` Patrick McHardy
2006-05-31  0:35       ` Pablo Neira Ayuso
2006-05-31  1:01         ` Patrick McHardy
2006-06-06 11:35           ` Pablo Neira Ayuso
2006-06-08  7:25             ` Patrick McHardy [this message]
2006-06-11 22:00               ` Pablo Neira Ayuso
2006-06-06 17:27           ` 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=4487D0E2.4030705@trash.net \
    --to=kaber@trash.net \
    --cc=eric@inl.fr \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=pablo@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.