From: Steen Hegelund <steen.hegelund@microchip.com>
To: "David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: Steen Hegelund <steen.hegelund@microchip.com>,
<UNGLinuxDriver@microchip.com>,
Randy Dunlap <rdunlap@infradead.org>,
"Casper Andersson" <casper.casan@gmail.com>,
Russell King <rmk+kernel@armlinux.org.uk>,
Wan Jiabing <wanjiabing@vivo.com>,
"Nathan Huckleberry" <nhuck@google.com>,
<linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
"Steen Hegelund" <Steen.Hegelund@microchip.com>,
Daniel Machon <daniel.machon@microchip.com>,
Horatiu Vultur <horatiu.vultur@microchip.com>,
Lars Povlsen <lars.povlsen@microchip.com>,
Dan Carpenter <error27@gmail.com>,
Michael Walle <michael@walle.cc>
Subject: [PATCH net-next 0/5] Improve locking in the VCAP API
Date: Tue, 17 Jan 2023 09:55:39 +0100 [thread overview]
Message-ID: <20230117085544.591523-1-steen.hegelund@microchip.com> (raw)
This improves the VCAP cache and the VCAP rule list protection against
access from different sources.
The VCAP Admin lock protects the list of rules for the VCAP instance as
well as the cache used for encoding and decoding rules.
This series provides dedicated functions for accessing rule statistics,
decoding rule content, verifying if a rule exists and getting a rule with
the lock held, as well as ensuring the use of the lock when the list of
rules or the cache is accessed.
Steen Hegelund (5):
net: microchip: sparx5: Add support for rule count by cookie
net: microchip: sparx5: Add support to check for existing VCAP rule id
net: microchip: sparx5: Add VCAP admin locking in debugFS
net: microchip: sparx5: Improve VCAP admin locking in the VCAP API
net: microchip: sparx5: Add lock initialization to the KUNIT tests
.../microchip/sparx5/sparx5_tc_flower.c | 34 +--
.../net/ethernet/microchip/vcap/vcap_api.c | 234 ++++++++++++------
.../ethernet/microchip/vcap/vcap_api_client.h | 2 +
.../microchip/vcap/vcap_api_debugfs.c | 14 +-
.../microchip/vcap/vcap_api_debugfs_kunit.c | 1 +
.../ethernet/microchip/vcap/vcap_api_kunit.c | 1 +
.../microchip/vcap/vcap_api_private.h | 3 +
7 files changed, 175 insertions(+), 114 deletions(-)
--
2.39.0
next reply other threads:[~2023-01-17 8:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 8:55 Steen Hegelund [this message]
2023-01-17 8:55 ` [PATCH net-next 1/5] net: microchip: sparx5: Add support for rule count by cookie Steen Hegelund
2023-01-17 8:55 ` [PATCH net-next 2/5] net: microchip: sparx5: Add support to check for existing VCAP rule id Steen Hegelund
2023-01-17 8:55 ` [PATCH net-next 3/5] net: microchip: sparx5: Add VCAP admin locking in debugFS Steen Hegelund
2023-01-17 8:55 ` [PATCH net-next 4/5] net: microchip: sparx5: Improve VCAP admin locking in the VCAP API Steen Hegelund
2023-01-17 8:55 ` [PATCH net-next 5/5] net: microchip: sparx5: Add lock initialization to the KUNIT tests Steen Hegelund
2023-01-18 14:40 ` [PATCH net-next 0/5] Improve locking in the VCAP API patchwork-bot+netdevbpf
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=20230117085544.591523-1-steen.hegelund@microchip.com \
--to=steen.hegelund@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=casper.casan@gmail.com \
--cc=daniel.machon@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=error27@gmail.com \
--cc=horatiu.vultur@microchip.com \
--cc=kuba@kernel.org \
--cc=lars.povlsen@microchip.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@walle.cc \
--cc=netdev@vger.kernel.org \
--cc=nhuck@google.com \
--cc=pabeni@redhat.com \
--cc=rdunlap@infradead.org \
--cc=rmk+kernel@armlinux.org.uk \
--cc=wanjiabing@vivo.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
all inboxes | Powered by JetHome®