mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Martin Josefsson <gandalf@wlug.westbo.se>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com,
	bert hubert <ahu@ds9a.nl>
Subject: Re: Route cache performance under stress
Date: 05 Apr 2003 20:17:09 +0200	[thread overview]
Message-ID: <1049566629.25170.203.camel@tux.rsn.bth.se> (raw)
In-Reply-To: <8765pshpd4.fsf@deneb.enyo.de>

On Sat, 2003-04-05 at 18:37, Florian Weimer wrote:

> Netfilter ip_conntrack support might have similar issues, but you
> can't use it in a uncooperative environment anyway, at least in my
> experience.  (Note that there appears to be no way to disable
> connection tracking while the code is in the kernel.)

It's correct that ip_conntrack has similar issues. There's been some
work on the hashalgorithm used but no patch has been made yet.
And yes it doesn't scale well at all (especially on SMP), I'm about to
start working on this a bit. Hopefully I can improve it somewhat.

If you've compiled ip_conntrack into your kernel there's only two ways
to disable it and both needs code-modifications :)

Install a netfilter-module that gets the packets before conntrack and
steal the packets, the downside is that you will bypass the rest of
iptables as well.

Apply a patch from patch-o-matic that adds a NOTRACK target that
instructs conntrack to not look at the packets marked by that target.

-- 
/Martin

  reply	other threads:[~2003-04-05 18:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-05 16:37 Florian Weimer
2003-04-05 18:17 ` Martin Josefsson [this message]
2003-04-05 18:34 ` Willy Tarreau
2003-05-16 22:24 ` Simon Kirby
2003-05-16 23:16   ` Florian Weimer
2003-05-19 19:10     ` Simon Kirby
2003-05-17  2:35   ` David S. Miller
2003-05-17  7:31     ` Florian Weimer
2003-05-17 22:09       ` David S. Miller
2003-05-18  9:21         ` Florian Weimer
2003-05-18  9:31           ` David S. Miller
2003-05-19 17:36             ` Jamal Hadi
2003-05-19 19:18               ` Ralph Doncaster
2003-04-08  6:14 Scott A Crosby

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=1049566629.25170.203.camel@tux.rsn.bth.se \
    --to=gandalf@wlug.westbo.se \
    --cc=ahu@ds9a.nl \
    --cc=fw@deneb.enyo.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®