From: Ioana Ciornei <ciorneiioana@gmail.com>
To: davem@davemloft.net, kuba@kernel.org
Cc: netdev@vger.kernel.org, ruxandra.radulescu@nxp.com,
Ioana Ciornei <ioana.ciornei@nxp.com>
Subject: Re: [PATCH net-next 0/5] dpaa2-switch: add tc hardware offload on ingress traffic
Date: Wed, 14 Apr 2021 18:17:28 +0300 [thread overview]
Message-ID: <20210414151728.amjvjgnqlejrujwr@skbuf> (raw)
In-Reply-To: <20210413132448.4141787-1-ciorneiioana@gmail.com>
On Tue, Apr 13, 2021 at 04:24:43PM +0300, Ioana Ciornei wrote:
> From: Ioana Ciornei <ioana.ciornei@nxp.com>
>
> This patch set adds tc hardware offload on ingress traffic in
> dpaa2-switch. The cls flower and matchall classifiers are supported
> using the same ACL infrastructure supported by the dpaa2-switch.
>
> The first patch creates a new structure to hold all the necessary
> information related to an ACL table. This structure is used in the next
> patches to create a link between each switch port and the table used.
> Multiple ports can share the same ACL table when they also share the
> ingress tc block. Also, some small changes in the priority of the
> default STP trap is done in the second patch.
>
> The support for cls flower is added in the 3rd patch, while the 4th
> one builds on top of the infrastructure put in place and adds cls
> matchall support.
>
> The following flow keys are supported:
> - Ethernet: dst_mac/src_mac
> - IPv4: dst_ip/src_ip/ip_proto/tos
> - VLAN: vlan_id/vlan_prio/vlan_tpid/vlan_dei
> - L4: dst_port/src_port
>
> Each filter can support only one action from the following list:
> - drop
> - mirred egress redirect
> - trap
>
> With the last patch, we reuse the dpaa2_switch_acl_entry_add() function
> added previously instead of open-coding the install of a new ACL entry
> into the table.
>
> Ioana Ciornei (5):
> dpaa2-switch: create a central dpaa2_switch_acl_tbl structure
> dpaa2-switch: install default STP trap rule with the highest priority
> dpaa2-switch: add tc flower hardware offload on ingress traffic
> dpaa2-switch: add tc matchall filter support
> dpaa2-switch: reuse dpaa2_switch_acl_entry_add() for STP frames trap
>
This patch set is in the 'Accepted' state in patchwork but is nowhere to
be found in the net-next tree.
Should I do something else or it was just not pushed yet?
Ioana
next prev parent reply other threads:[~2021-04-14 15:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 13:24 [PATCH net-next 0/5] dpaa2-switch: add tc hardware offload on ingress traffic Ioana Ciornei
2021-04-13 13:24 ` [PATCH net-next 1/5] dpaa2-switch: create a central dpaa2_switch_acl_tbl structure Ioana Ciornei
2021-04-13 13:24 ` [PATCH net-next 2/5] dpaa2-switch: install default STP trap rule with the highest priority Ioana Ciornei
2021-04-13 13:24 ` [PATCH net-next 3/5] dpaa2-switch: add tc flower hardware offload on ingress traffic Ioana Ciornei
2021-04-13 13:24 ` [PATCH net-next 4/5] dpaa2-switch: add tc matchall filter support Ioana Ciornei
2021-04-13 13:24 ` [PATCH net-next 5/5] dpaa2-switch: reuse dpaa2_switch_acl_entry_add() for STP frames trap Ioana Ciornei
2021-04-14 15:17 ` Ioana Ciornei [this message]
2021-04-14 19:48 ` [PATCH net-next 0/5] dpaa2-switch: add tc hardware offload on ingress traffic 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=20210414151728.amjvjgnqlejrujwr@skbuf \
--to=ciorneiioana@gmail.com \
--cc=davem@davemloft.net \
--cc=ioana.ciornei@nxp.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ruxandra.radulescu@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;
as well as URLs for NNTP newsgroup(s).