All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: Jesper Dangaard Brouer <jbrouer@redhat.com>
Cc: David Miller <davem@davemloft.net>,
	netdev@vger.kernel.org, eric.dumazet@gmail.com
Subject: Re: [PATCH net] inet: limit length of fragment queue hash table bucket lists
Date: Tue, 19 Mar 2013 15:31:13 +0100	[thread overview]
Message-ID: <20130319143113.GA24909@order.stressinduktion.org> (raw)
In-Reply-To: <1363702840.3232.104.camel@localhost>

On Tue, Mar 19, 2013 at 03:20:40PM +0100, Jesper Dangaard Brouer wrote:
> I think it's overkill to implement this now.  I just want this patch in
> as a safeguard.
> 
> The idea I discussed with Eric, will remove the need for this patch.
> The idea is to drop the LRU lists, increase the hash size a bit, and do
> cleanup/eviction directly on the frag hash tables.  And e.g. only allow
> 5 frag queue elements in each hash bucket... but more work and testing
> is needed before I have something ready.

Thats cool, I won't rebase the patch.

Thanks,

  Hannes

  parent reply	other threads:[~2013-03-19 14:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-15 21:32 [PATCH net] inet: limit length of fragment queue hash table bucket lists Hannes Frederic Sowa
2013-03-19 14:03 ` David Miller
2013-03-19 14:08   ` Hannes Frederic Sowa
2013-03-19 14:15   ` Eric Dumazet
2013-03-19 14:22     ` Hannes Frederic Sowa
2013-03-19 14:20   ` Jesper Dangaard Brouer
2013-03-19 14:28     ` David Miller
2013-03-19 14:31     ` Hannes Frederic Sowa [this message]
2013-03-19 14:29 ` David Miller

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=20130319143113.GA24909@order.stressinduktion.org \
    --to=hannes@stressinduktion.org \
    --cc=davem@davemloft.net \
    --cc=eric.dumazet@gmail.com \
    --cc=jbrouer@redhat.com \
    --cc=netdev@vger.kernel.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.