From: Volodymyr Mytnyk <volodymyr.mytnyk@plvision.eu>
To: netdev@vger.kernel.org
Cc: Taras Chornyi <taras.chornyi@plvision.eu>,
Mickey Rachamim <mickeyr@marvell.com>,
Serhiy Pshyk <serhiy.pshyk@plvision.eu>,
Volodymyr Mytnyk <vmytnyk@marvell.com>,
Taras Chornyi <tchornyi@marvell.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
linux-kernel@vger.kernel.org
Subject: [PATCH net-next 0/3] net: prestera: acl: migrate to new vTcam/counter api
Date: Tue, 23 Nov 2021 18:57:59 +0200 [thread overview]
Message-ID: <1637686684-2492-1-git-send-email-volodymyr.mytnyk@plvision.eu> (raw)
From: Volodymyr Mytnyk <vmytnyk@marvell.com>
This patch series aims to use new vTcam and Counter API
provided by latest fw version. The advantage of using
this API is the following:
- provides a way to have a rule with desired Tcam size (improves
Tcam memory utilization).
- batch support for acl counters gathering (improves performance)
- gives more control over HW ACL engine (actions/matches/bindings)
to be able to support more features in the future driver
versions
Note: the feature set left the same as was before this patch.
Volodymyr Mytnyk (3):
net: prestera: acl: migrate to new vTCAM api
net: prestera: add counter HW API
net: prestera: acl: add rule stats support
drivers/net/ethernet/marvell/prestera/Makefile | 2 +-
drivers/net/ethernet/marvell/prestera/prestera.h | 1 +
.../net/ethernet/marvell/prestera/prestera_acl.c | 699 +++++++++++++++------
.../net/ethernet/marvell/prestera/prestera_acl.h | 215 ++++---
.../ethernet/marvell/prestera/prestera_counter.c | 474 ++++++++++++++
.../ethernet/marvell/prestera/prestera_counter.h | 30 +
.../net/ethernet/marvell/prestera/prestera_flow.c | 109 +++-
.../net/ethernet/marvell/prestera/prestera_flow.h | 16 +
.../ethernet/marvell/prestera/prestera_flower.c | 288 ++++-----
.../ethernet/marvell/prestera/prestera_flower.h | 12 +-
.../net/ethernet/marvell/prestera/prestera_hw.c | 491 ++++++++-------
.../net/ethernet/marvell/prestera/prestera_hw.h | 62 +-
.../net/ethernet/marvell/prestera/prestera_main.c | 8 +
.../net/ethernet/marvell/prestera/prestera_span.c | 1 +
14 files changed, 1744 insertions(+), 664 deletions(-)
create mode 100644 drivers/net/ethernet/marvell/prestera/prestera_counter.c
create mode 100644 drivers/net/ethernet/marvell/prestera/prestera_counter.h
--
2.7.4
next reply other threads:[~2021-11-23 16:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-23 16:57 Volodymyr Mytnyk [this message]
2021-11-23 16:58 ` [PATCH net-next 1/3] net: prestera: acl: migrate to new vTCAM api Volodymyr Mytnyk
2021-11-25 3:15 ` Jakub Kicinski
2021-11-30 12:26 ` Volodymyr Mytnyk [C]
2021-11-25 3:17 ` Jakub Kicinski
2021-11-23 16:58 ` [PATCH net-next 2/3] net: prestera: add counter HW API Volodymyr Mytnyk
2021-11-25 3:16 ` Jakub Kicinski
2021-11-30 12:28 ` Volodymyr Mytnyk [C]
2021-11-23 16:58 ` [PATCH net-next 3/3] net: prestera: acl: add rule stats support Volodymyr Mytnyk
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=1637686684-2492-1-git-send-email-volodymyr.mytnyk@plvision.eu \
--to=volodymyr.mytnyk@plvision.eu \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mickeyr@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=serhiy.pshyk@plvision.eu \
--cc=taras.chornyi@plvision.eu \
--cc=tchornyi@marvell.com \
--cc=vmytnyk@marvell.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).