From mboxrd@z Thu Jan 1 00:00:00 1970 From: Murali Karicheri Subject: Re: Enable and configure storm prevention in a network device Date: Mon, 9 Apr 2018 10:33:49 -0400 Message-ID: <1847a659-dac5-06b5-072f-a3eda17bfaf1@ti.com> References: <76c2b7c7-4f85-c81e-c928-e5650cc26b93@ti.com> <20180405.162031.2009953983418308744.davem@davemloft.net> <75eb56a4-ded2-5ed5-116c-776312f93cf3@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Cc: , To: Florian Fainelli , David Miller Return-path: Received: from fllnx209.ext.ti.com ([198.47.19.16]:46181 "EHLO fllnx209.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752298AbeDIObS (ORCPT ); Mon, 9 Apr 2018 10:31:18 -0400 In-Reply-To: <75eb56a4-ded2-5ed5-116c-776312f93cf3@gmail.com> Content-Language: en-US Sender: netdev-owner@vger.kernel.org List-ID: On 04/05/2018 06:35 PM, Florian Fainelli wrote: > On 04/05/2018 01:20 PM, David Miller wrote: >> From: Murali Karicheri >> Date: Thu, 5 Apr 2018 16:14:49 -0400 >> >>> Is there a standard way to implement and configure storm prevention >>> in a Linux network device? >> >> What kind of "storm", an interrupt storm? >> > > I would assume Murali is referring to L2 broadcast storms which is > common in switches. There is not an API for that AFAICT and I am not > sure what a proper API would look like. > Thanks Florian for adding more details. Yes, I am referring to L2 broadcast or multicast storm. At this point I don't see a reason why to exclude unicast storm as well if the hardware has the capability. -- Murali Karicheri Linux Kernel, Keystone