From: Max Kellermann <max@duempel.org>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: conntrackd: questions about the new alarm implementation
Date: Mon, 21 Jan 2008 14:33:13 +0100 [thread overview]
Message-ID: <20080121133313.GA32375@swift.blarg.de> (raw)
In-Reply-To: <47949BAF.6020203@netfilter.org>
On 2008/01/21 14:18, Pablo Neira Ayuso <pablo@netfilter.org> wrote:
> Sure. Current approach gives good results to my benchmarks and I can
> make peace since it's not linear anymore ;).
It's still linear. add_alarm() is still O(n), or better: it is
O(n/2048) which is mathematically the same as O(n). But you made
everything else O(n*2048) = O(n), which is why I dislike this
optimization - you optimized for one artificial test case, penalizing
the majority of conntrackd users who don't have 25.000 connections.
Max
next prev parent reply other threads:[~2008-01-21 13:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-21 6:20 conntrackd: questions about the new alarm implementation Max Kellermann
2008-01-21 12:55 ` Pablo Neira Ayuso
2008-01-21 13:05 ` Max Kellermann
2008-01-21 13:18 ` Pablo Neira Ayuso
2008-01-21 13:33 ` Max Kellermann [this message]
2008-01-21 13:52 ` 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=20080121133313.GA32375@swift.blarg.de \
--to=max@duempel.org \
--cc=netfilter-devel@vger.kernel.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.