From: Vladimir Oltean <olteanv@gmail.com>
To: Grygorii Strashko <grygorii.strashko@ti.com>
Cc: "David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, Jakub Kicinski <kuba@kernel.org>,
Vignesh Raghavendra <vigneshr@ti.com>,
Sekhar Nori <nsekhar@ti.com>,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
Tony Lindgren <tony@atomide.com>
Subject: Re: [PATCH net-next 2/3] net: ethernet: ti: cpsw_new: enable broadcast/multicast rate limit support
Date: Sat, 14 Nov 2020 21:09:09 +0200 [thread overview]
Message-ID: <20201114190909.cc3rlnvom6wf2zkg@skbuf> (raw)
In-Reply-To: <20201114035654.32658-3-grygorii.strashko@ti.com>
On Sat, Nov 14, 2020 at 05:56:53AM +0200, Grygorii Strashko wrote:
> This patch enables support for ingress broadcast(BC)/multicast(MC) rate limiting
> in TI CPSW switchdev driver (the corresponding ALE support was added in previous
> patch) by implementing HW offload for simple tc-flower policer with matches
> on dst_mac:
> - ff:ff:ff:ff:ff:ff has to be used for BC rate limiting
> - 01:00:00:00:00:00 fixed value has to be used for MC rate limiting
>
> Hence tc policer defines rate limit in terms of bits per second, but the
> ALE supports limiting in terms of packets per second - the rate limit
> bits/sec is converted to number of packets per second assuming minimum
> Ethernet packet size ETH_ZLEN=60 bytes.
>
> Examples:
> - BC rate limit to 1000pps:
> tc qdisc add dev eth0 clsact
> tc filter add dev eth0 ingress flower skip_sw dst_mac ff:ff:ff:ff:ff:ff \
> action police rate 480kbit burst 64k
>
> rate 480kbit - 1000pps * 60 bytes * 8, burst - not used.
>
> - MC rate limit to 20000pps:
> tc qdisc add dev eth0 clsact
> tc filter add dev eth0 ingress flower skip_sw dst_mac 01:00:00:00:00:00 \
> action police rate 9600kbit burst 64k
>
> rate 9600kbit - 20000pps * 60 bytes * 8, burst - not used.
>
> Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com>
> ---
Your example for multicast would actually be correct if you specified
the mask as well. Like this:
tc filter add dev eth0 ingress flower skip_sw \
dst_mac 01:00:00:00:00:00/01:00:00:00:00:00 \
action police rate 9600kbit burst 64k
But as things stand, the flow rule would have a certain meaning in
software (rate-limit only that particular multicast MAC address) and a
different meaning in hardware. Please modify the driver code to also
match on the mask.
next prev parent reply other threads:[~2020-11-14 19:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-14 3:56 [PATCH net-next 0/3] net: ethernet: ti: cpsw: enable broadcast/multicast rate limit support Grygorii Strashko
2020-11-14 3:56 ` [PATCH net-next 1/3] drivers: net: cpsw: ale: add " Grygorii Strashko
2020-11-14 3:56 ` [PATCH net-next 2/3] net: ethernet: ti: cpsw_new: enable " Grygorii Strashko
2020-11-14 19:09 ` Vladimir Oltean [this message]
2020-11-16 13:01 ` Grygorii Strashko
2020-11-14 3:56 ` [PATCH net-next 3/3] net: ethernet: ti: am65-cpsw: " Grygorii Strashko
2020-11-14 19:17 ` Vladimir Oltean
2020-11-16 18:39 ` Grygorii Strashko
2020-11-16 18:59 ` Vladimir Oltean
2020-11-16 23:30 ` Andrew Lunn
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=20201114190909.cc3rlnvom6wf2zkg@skbuf \
--to=olteanv@gmail.com \
--cc=davem@davemloft.net \
--cc=grygorii.strashko@ti.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=tony@atomide.com \
--cc=vigneshr@ti.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