From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: Joergen Andreasen <joergen.andreasen@microchip.com>
Cc: Linux Netdev List <netdev@vger.kernel.org>,
Microchip Linux Driver Support <UNGLinuxDriver@microchip.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
"David S. Miller" <davem@davemloft.net>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next v3 1/1] net: mscc: ocelot: Implement port policers via tc command
Date: Tue, 28 May 2019 13:15:53 -0700 [thread overview]
Message-ID: <CAJpBn1zrkKMteogJt__6zx6gE+=pO2P5Opv0fSNhZNm9GLGWDQ@mail.gmail.com> (raw)
On Tue, 28 May 2019 14:49:17 +0200, Joergen Andreasen wrote:
> Hardware offload of matchall classifier and police action are now
> supported via the tc command.
> Supported police parameters are: rate and burst.
>
> Example:
>
> Add:
> tc qdisc add dev eth3 handle ffff: ingress
> tc filter add dev eth3 parent ffff: prio 1 handle 2 \
> matchall skip_sw \
> action police rate 100Mbit burst 10000
>
> Show:
> tc -s -d qdisc show dev eth3
> tc -s -d filter show dev eth3 ingress
>
> Delete:
> tc filter del dev eth3 parent ffff: prio 1
> tc qdisc del dev eth3 handle ffff: ingress
>
> Signed-off-by: Joergen Andreasen <joergen.andreasen@microchip.com>
Looks reasonable :)
Acked-by: Jakub Kicinski <jakub.kicinski@netronome.com>
next reply other threads:[~2019-05-28 20:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 20:15 Jakub Kicinski [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-05-02 9:40 [PATCH net-next 0/3] Add hw offload of TC police on MSCC ocelot Joergen Andreasen
2019-05-28 12:49 ` [PATCH net-next v3 0/1] " Joergen Andreasen
2019-05-28 12:49 ` [PATCH net-next v3 1/1] net: mscc: ocelot: Implement port policers via tc command Joergen Andreasen
2019-05-30 4:38 ` David Miller
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='CAJpBn1zrkKMteogJt__6zx6gE+=pO2P5Opv0fSNhZNm9GLGWDQ@mail.gmail.com' \
--to=jakub.kicinski@netronome.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=davem@davemloft.net \
--cc=joergen.andreasen@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).