From: Jakub Kicinski <kuba@kernel.org>
To: Grygorii Strashko <grygorii.strashko@ti.com>
Cc: "David S. Miller" <davem@davemloft.net>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Kishon Vijay Abraham I <kishon@ti.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
<linux-omap@vger.kernel.org>, Tony Lindgren <tony@atomide.com>,
Andrew Lunn <andrew@lunn.ch>,
Vladimir Oltean <vladimir.oltean@nxp.com>
Subject: Re: [PATCH net-next v2 2/3] net: ethernet: ti: am65-cpsw: enable bc/mc storm prevention support
Date: Tue, 2 Nov 2021 17:38:40 -0700 [thread overview]
Message-ID: <20211102173840.01f464ec@kicinski-fedora-PC1C0HJN> (raw)
In-Reply-To: <20211101170122.19160-3-grygorii.strashko@ti.com>
On Mon, 1 Nov 2021 19:01:21 +0200 Grygorii Strashko wrote:
> - 01:00:00:00:00:00 fixed value has to be used for MC packets rate
> limiting (exact match)
This looks like a stretch, why not use a mask? You can require users to
always install both BC and MC rules if you want to make sure the masked
rule does not match BC.
next prev parent reply other threads:[~2021-11-03 0:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 17:01 [PATCH net-next v2 0/3] net: ethernet: ti: cpsw: enable bc/mc storm prevention support Grygorii Strashko
2021-11-01 17:01 ` [PATCH net-next v2 1/3] drivers: net: cpsw: ale: add broadcast/multicast rate limit support Grygorii Strashko
2021-11-01 17:01 ` [PATCH net-next v2 2/3] net: ethernet: ti: am65-cpsw: enable bc/mc storm prevention support Grygorii Strashko
2021-11-03 0:38 ` Jakub Kicinski [this message]
2021-11-03 22:20 ` Grygorii Strashko
2021-11-03 23:07 ` Jakub Kicinski
2021-11-03 23:19 ` Grygorii Strashko
2021-11-01 17:01 ` [PATCH net-next v2 3/3] net: ethernet: ti: cpsw_new: " Grygorii Strashko
2021-11-01 23:53 ` [PATCH net-next v2 0/3] net: ethernet: ti: cpsw: " Vladimir Oltean
2021-11-02 12:36 ` Grygorii Strashko
2021-11-02 14:38 ` Vladimir Oltean
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=20211102173840.01f464ec@kicinski-fedora-PC1C0HJN \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=grygorii.strashko@ti.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tony@atomide.com \
--cc=vigneshr@ti.com \
--cc=vladimir.oltean@nxp.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox