From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Dumazet Subject: Re: [PATCH net] inet: limit length of fragment queue hash table bucket lists Date: Tue, 19 Mar 2013 07:15:43 -0700 Message-ID: <1363702543.2558.2.camel@edumazet-glaptop> References: <20130315213230.GB24041@order.stressinduktion.org> <20130319.100324.927922515830950770.davem@davemloft.net> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: hannes@stressinduktion.org, netdev@vger.kernel.org, jbrouer@redhat.com To: David Miller Return-path: Received: from mail-pb0-f54.google.com ([209.85.160.54]:60769 "EHLO mail-pb0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752296Ab3CSOPq (ORCPT ); Tue, 19 Mar 2013 10:15:46 -0400 Received: by mail-pb0-f54.google.com with SMTP id rr4so467364pbb.13 for ; Tue, 19 Mar 2013 07:15:45 -0700 (PDT) In-Reply-To: <20130319.100324.927922515830950770.davem@davemloft.net> Sender: netdev-owner@vger.kernel.org List-ID: On Tue, 2013-03-19 at 10:03 -0400, David Miller wrote: > From: Hannes Frederic Sowa > Date: Fri, 15 Mar 2013 22:32:30 +0100 > > > This patch introduces a constant limit of the fragment queue hash > > table bucket list lengths. Currently the limit 128 is choosen somewhat > > arbitrary and just ensures that we can fill up the fragment cache with > > empty packets up to the default ip_frag_high_thresh limits. It should > > just protect from list iteration eating considerable amounts of cpu. > > > > If we reach the maximum length in one hash bucket a warning is printed. > > This is implemented on the caller side of inet_frag_find to distinguish > > between the different users of inet_fragment.c. > > > > I dropped the out of memory warning in the ipv4 fragment lookup path, > > because we already get a warning by the slab allocator. > > > > Cc: Eric Dumazet > > Cc: Jesper Dangaard Brouer > > Signed-off-by: Hannes Frederic Sowa > > This looks mostly fine to me, Eric could you give it a quick review? > Sure, it looks ok for me Acked-by: Eric Dumazet > Although one comment from me: > > > +/* averaged: > > + * max_depth = default ipfrag_high_thresh / INETFRAGS_HASHSZ / > > + * rounded up (SKB_TRUELEN(0) + sizeof(struct ipq or > > + * struct frag_queue)) > > + */ > > +#define INETFRAGS_MAXDEPTH 128 > > If we deem this to be the ideal formula, maybe we can maintain it > accurately and very cheaply at run time. We'd do this by adding a > handler for the ipfrag_high_thresh sysctl, and use that to recalculate > the maxdepth any time ipfrag_high_thresh is changed by the user. This can probably be done in a second patch for net-next