From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andrew Lunn <andrew@lunn.ch>
Subject: Re: [PATCH] net: bridge: add max_fdb_count
Date: Fri, 17 Nov 2017 15:06:23 +0100
Message-ID: <20171117140623.GA5809@lunn.ch>
References: <1510774027-2468-1-git-send-email-srn@prgmr.com>
 <4f31ae8b-352e-d2ab-cd71-4b31f76e666a@cumulusnetworks.com>
 <4d756a43-e51d-c52d-7b4b-fce61f021a66@prgmr.com>
 <20171116095846.GB14616@1wt.eu>
 <3d08c77f-8d71-e302-d3f7-24acc6df9414@prgmr.com>
 <20171116192325.GA16122@lunn.ch>
 <m3ineaoty4.fsf@luffy.cx>
 <20171116162718.3c252ff1@xeon-e3>
 <20171117052608.GB16950@1wt.eu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: Stephen Hemminger <stephen@networkplumber.org>,
        Vincent Bernat <bernat@luffy.cx>, Sarah Newman <srn@prgmr.com>,
        Nikolay Aleksandrov <nikolay@cumulusnetworks.com>,
        netdev@vger.kernel.org, roopa <roopa@cumulusnetworks.com>
To: Willy Tarreau <w@1wt.eu>
Return-path: <netdev-owner@vger.kernel.org>
Received: from vps0.lunn.ch ([185.16.172.187]:58465 "EHLO vps0.lunn.ch"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S934020AbdKQOGb (ORCPT <rfc822;netdev@vger.kernel.org>);
        Fri, 17 Nov 2017 09:06:31 -0500
Content-Disposition: inline
In-Reply-To: <20171117052608.GB16950@1wt.eu>
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>

> Usually it's better to apply LRU or random here in my opinion, as the
> new entry is much more likely to be needed than older ones by definition.

Hi Willy

I think this depends on why you need to discard. If it is normal
operation and the limits are simply too low, i would agree.

If however it is a DoS, throwing away the new entries makes sense,
leaving the old ones which are more likely to be useful.

Most of the talk in this thread has been about limits for DoS
prevention...

	Andrew