All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Jan Engelhardt <jengelh@computergmbh.de>,
	Vasily Averin <vvs@sw.ru>,
	netfilter-devel@lists.netfilter.org, devel@openvz.org,
	Eric Dumazet <dada1@cosmosbay.com>
Subject: Re: [NETFILTER] early_drop() imrovement (v4)
Date: Tue, 03 Jul 2007 13:42:54 +0200	[thread overview]
Message-ID: <468A363E.7070700@trash.net> (raw)
In-Reply-To: <1183406199.16922.10.camel@localhost.localdomain>

Rusty Russell wrote:
> On Wed, 2007-06-27 at 15:54 +0200, Patrick McHardy wrote:
> 
>>[NETFILTER]: nf_conntrack: early_drop improvement
>
> This looks good.  The randomness in the hash means we no longer need the
> "hit the same hash bucket" heuristic to avoid hashbombing.
> 
> I still wonder if we should batch up the drops a little while we're
> doing all this work?  Should reduce stress under serious flood load.


Good point, I didn't think of that. Its a bit tricky though, we can't
destroy them while holding nf_conntrack_lock, so we'd either have to
release and re-grab it for every conntrack we want to kill or write
lock it from the beginning, clean them from the lists immediately and
put them on a temporary destruction queue. Or split death_by_timeout
so it can deal with callers already holding nf_conntrack_lock ..

I'll see if I can come up with a halfway decent looking patch :)

      parent reply	other threads:[~2007-07-03 11:42 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-06  8:00 [PATCH 2.6.21-rc6] [netfilter] early_drop imrovement Vasily Averin
2007-04-06  8:24 ` Eric Dumazet
2007-04-06 10:26   ` Vasily Averin
2007-04-06 15:08     ` Patrick McHardy
2007-04-06 15:08       ` Patrick McHardy
2007-04-07 11:45       ` [PATCH nf-2.6.22] " Vasily Averin
2007-04-07 12:08         ` Eric Dumazet
2007-04-07 12:08           ` Eric Dumazet
2007-04-08  5:02           ` Vasily Averin
2007-05-09  6:59             ` [NETFILTER] early_drop() imrovement (v3) Vasily Averin
2007-06-25 13:53               ` Patrick McHardy
2007-06-25 14:36                 ` Jan Engelhardt
2007-06-26 13:20                 ` Vasily Averin
2007-06-26 13:27                   ` Patrick McHardy
2007-06-27  8:46                   ` [NETFILTER] early_drop() imrovement (v4) Vasily Averin
2007-06-27  8:52                     ` Patrick McHardy
2007-06-27  8:52                       ` Patrick McHardy
2007-06-27 12:04                       ` Patrick McHardy
2007-06-27 12:29                         ` Vasily Averin
2007-06-27 12:51                           ` Patrick McHardy
2007-06-27 13:02                             ` Vasily Averin
2007-06-27 13:18                               ` Patrick McHardy
2007-06-27 13:23                                 ` Patrick McHardy
2007-06-27 13:25                                 ` Vasily Averin
2007-06-27 13:28                                   ` Patrick McHardy
2007-06-27 13:35                                     ` Patrick McHardy
2007-06-27 13:54                                       ` Patrick McHardy
2007-07-02 19:56                                         ` Rusty Russell
2007-07-03  6:39                                           ` Martin Josefsson
2007-07-03 11:42                                           ` Patrick McHardy [this message]

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=468A363E.7070700@trash.net \
    --to=kaber@trash.net \
    --cc=dada1@cosmosbay.com \
    --cc=devel@openvz.org \
    --cc=jengelh@computergmbh.de \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=rusty@rustcorp.com.au \
    --cc=vvs@sw.ru \
    /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.