From: patchwork-bot+netdevbpf@kernel.org
To: Daniel Machon <daniel.machon@microchip.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@kernel.org,
kuba@kernel.org, pabeni@redhat.com, Steen.Hegelund@microchip.com,
UNGLinuxDriver@microchip.com, robert.marko@sartura.hr,
netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v3 0/5] net: sparx5: add tc matchall port policer offload
Date: Wed, 11 Nov 2026 22:40:07 +0000 [thread overview]
Message-ID: <179443680768.1682529.11013685548418051653.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261105-b4-lan966x-pci-fdma-sparx5-lan969x-port-policers-v3-0-b45a3a26bed5@microchip.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 5 Nov 2026 14:19:34 +0100 you wrote:
> This series adds offload of tc matchall filters with a police action to
> the ingress port policers of Sparx5 and lan969x, which are both served
> by the sparx5 driver.
>
> In hardware, each ingress port has four single-rate leaky bucket
> policers. A policer drops the frames that exceed its rate and burst.
> The four policers of a port share the pass and drop statistics counters
> of the port.
>
> [...]
Here is the summary with links:
- [net-next,v3,1/5] net: sparx5: Drop redundant POL_ prefix from POL_UPD_INT_CFG
https://git.kernel.org/netdev/net-next/c/de6c6d0fe1a2
- [net-next,v3,2/5] net: sparx5: Add registers used by the port policer
https://git.kernel.org/netdev/net-next/c/08543a66f15a
- [net-next,v3,3/5] net: sparx5: Track shared tc blocks and per-port policer state
https://git.kernel.org/netdev/net-next/c/54d7dad1a3bb
- [net-next,v3,4/5] net: sparx5: Add hardware programming for the port policer
https://git.kernel.org/netdev/net-next/c/b18f7b93e0f7
- [net-next,v3,5/5] net: sparx5: Offload tc port policers via matchall
https://git.kernel.org/netdev/net-next/c/a53151fbbcd6
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-11-11 22:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 13:19 Daniel Machon
2026-11-05 13:19 ` [PATCH net-next v3 1/5] net: sparx5: Drop redundant POL_ prefix from POL_UPD_INT_CFG Daniel Machon
2026-11-05 17:16 ` Mohsin Bashir
2026-11-05 13:19 ` [PATCH net-next v3 2/5] net: sparx5: Add registers used by the port policer Daniel Machon
2026-11-05 13:19 ` [PATCH net-next v3 3/5] net: sparx5: Track shared tc blocks and per-port policer state Daniel Machon
2026-11-05 13:19 ` [PATCH net-next v3 4/5] net: sparx5: Add hardware programming for the port policer Daniel Machon
2026-11-05 17:09 ` Mohsin Bashir
2026-11-06 7:45 ` Daniel Machon
2026-11-05 13:19 ` [PATCH net-next v3 5/5] net: sparx5: Offload tc port policers via matchall Daniel Machon
2026-11-11 22:40 ` patchwork-bot+netdevbpf [this message]
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=179443680768.1682529.11013685548418051653.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Steen.Hegelund@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew+netdev@lunn.ch \
--cc=daniel.machon@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robert.marko@sartura.hr \
/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
all inboxes | Powered by JetHome®