From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org 1D8C540A55 DKIM-Filter: OpenDKIM Filter v2.11.0 smtp2.osuosl.org 60D7C409A6 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nxp.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=q2eATHDWfBwliiKsDwyEf6GdLM9NZxOFrZgpWe1cZDo=; b=HqWpCL7x4GGoKPioHC2l5lJueLj0EESgmvqsNWhF7hlkzK36JLRU1spNaYpHh4T2KbCShPfebFQqkEOo9Qiie18iwVnKnkfckzB6Fmw1rGw57DbPpU5hjyZhK6KseKHqCRw4fdt9/gaSuYSfzQLq/3zIQfGjrD9Tg/wZmix5j28= Date: Tue, 16 May 2023 13:55:09 +0300 From: Vladimir Oltean Message-ID: <20230516105509.xaalfs77vrlr663u@skbuf> References: <20230515085046.4457-1-jnixdorf-oss@avm.de> <20230516102141.w75yh6pdo53ufjur@skbuf> <20230516104428.i5ou4ogx7gt2x6gq@skbuf> Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: MIME-Version: 1.0 Subject: Re: [Bridge] [PATCH net-next 1/2] bridge: Add a limit on FDB entries List-Id: Linux Ethernet Bridging List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Nikolay Aleksandrov Cc: Andrew Lunn , Florian Fainelli , Johannes Nixdorf , netdev@vger.kernel.org, Ido Schimmel , bridge@lists.linux-foundation.org, Oleksij Rempel , Eric Dumazet , Roopa Prabhu , Jakub Kicinski , Paolo Abeni , "David S. Miller" On Tue, May 16, 2023 at 01:47:47PM +0300, Nikolay Aleksandrov wrote: > Having the current count is just a helper, if you have a high limit dumping the table > and counting might take awhile. Thanks for the feedback, then we'll polish and move > on with the set for a global limit. Ok, but to be useful, the current count will have to be directly comparable to the limit, I guess. So the current count will also be for dynamically learned entries? Or is the plan to enforce the global limit for any kind of FDB entries?