From: Henrik Nordstrom <hno@marasystems.com>
To: Harald Welte <laforge@gnumonks.org>,
Martin Josefsson <gandalf@wlug.westbo.se>
Cc: Netfilter-devel <netfilter-devel@lists.samba.org>
Subject: Re: [PATCH] remove exessive timer updates (3/4)
Date: Wed, 12 Jun 2002 00:21:14 +0200 [thread overview]
Message-ID: <200206120021.15472@henrik.marasystems.com> (raw)
In-Reply-To: <20020611095922.G11177@sunbeam.de.gnumonks.org>
On Tuesday 11 June 2002 09:59, Harald Welte wrote:
> On Thu, Jun 06, 2002 at 02:24:04PM +0200, Martin Josefsson wrote:
> > This patch adds a check to ip_ct_refresh() so it doesn't update
> > the timer of a connection unless it's been >HZ ticks since the
> > last update. both del_timer() and add_timer() disables interrupts
> > while removing/inserting the timer, no reason to do this for each
> > packet.
>
> ok. I'm postponing this stuff for after 2.4.20 time, since for
> 2.4.19 we already have enough netfilter [and core networking
> changes], and for 2.4.20 there will be the newnat merge.
Haven't looked at the patch, but one thing to look out for is to make
sure timer transitions is not lost.
Unlike atime updates, conntrack timers vary in length depending on the
state. It would not be fun if a TIME_WAIT state got a timeout of
ESTABLISHED only because the transition was too quick to be noticed
by the timer update filter..
Regards
Henrik
next prev parent reply other threads:[~2002-06-11 22:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-06 12:24 [PATCH] remove exessive timer updates (3/4) Martin Josefsson
2002-06-08 7:37 ` Harald Welte
2002-06-08 15:03 ` Martin Josefsson
2002-06-09 17:17 ` Harald Welte
2002-06-11 7:59 ` Harald Welte
2002-06-11 22:21 ` Henrik Nordstrom [this message]
2002-06-12 9:10 ` Martin Josefsson
2002-06-12 19:02 ` Martin Josefsson
2002-06-13 12:07 ` Henrik Nordstrom
2002-06-13 16:17 ` Martin Josefsson
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=200206120021.15472@henrik.marasystems.com \
--to=hno@marasystems.com \
--cc=gandalf@wlug.westbo.se \
--cc=laforge@gnumonks.org \
--cc=netfilter-devel@lists.samba.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.