From: Jakub Kicinski <kuba@kernel.org>
To: idosch@nvidia.com, petrm@nvidia.com, simon.horman@corigine.com
Cc: netdev@vger.kernel.org, leonro@nvidia.com, jiri@resnulli.us,
Jakub Kicinski <kuba@kernel.org>
Subject: [RFT net-next 2/6] eth: nfp: wrap locking assertions in helpers
Date: Wed, 9 Mar 2022 16:16:28 -0800 [thread overview]
Message-ID: <20220310001632.470337-3-kuba@kernel.org> (raw)
In-Reply-To: <20220310001632.470337-1-kuba@kernel.org>
We can replace the PF lock with devlink instance lock in subsequent
changes. To make the patches easier to comprehend and limit line
lengths - factor out the existing locking assertions.
No functional changes.
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
---
drivers/net/ethernet/netronome/nfp/flower/main.c | 4 ++--
drivers/net/ethernet/netronome/nfp/nfp_app.c | 2 +-
drivers/net/ethernet/netronome/nfp/nfp_app.h | 9 +++++++++
drivers/net/ethernet/netronome/nfp/nfp_net_repr.c | 4 ++--
4 files changed, 14 insertions(+), 5 deletions(-)
diff --git a/drivers/net/ethernet/netronome/nfp/flower/main.c b/drivers/net/ethernet/netronome/nfp/flower/main.c
index ac1dcfa1d179..4d960a9641b3 100644
--- a/drivers/net/ethernet/netronome/nfp/flower/main.c
+++ b/drivers/net/ethernet/netronome/nfp/flower/main.c
@@ -266,7 +266,7 @@ nfp_flower_reprs_reify(struct nfp_app *app, enum nfp_repr_type type,
int i, err, count = 0;
reprs = rcu_dereference_protected(app->reprs[type],
- lockdep_is_held(&app->pf->lock));
+ nfp_app_is_locked(app));
if (!reprs)
return 0;
@@ -295,7 +295,7 @@ nfp_flower_wait_repr_reify(struct nfp_app *app, atomic_t *replies, int tot_repl)
if (!tot_repl)
return 0;
- lockdep_assert_held(&app->pf->lock);
+ assert_nfp_app_locked(app);
if (!wait_event_timeout(priv->reify_wait_queue,
atomic_read(replies) >= tot_repl,
NFP_FL_REPLY_TIMEOUT)) {
diff --git a/drivers/net/ethernet/netronome/nfp/nfp_app.c b/drivers/net/ethernet/netronome/nfp/nfp_app.c
index 3a973282b2bb..09f250e74dfa 100644
--- a/drivers/net/ethernet/netronome/nfp/nfp_app.c
+++ b/drivers/net/ethernet/netronome/nfp/nfp_app.c
@@ -121,7 +121,7 @@ struct nfp_reprs *
nfp_reprs_get_locked(struct nfp_app *app, enum nfp_repr_type type)
{
return rcu_dereference_protected(app->reprs[type],
- lockdep_is_held(&app->pf->lock));
+ nfp_app_is_locked(app));
}
struct nfp_reprs *
diff --git a/drivers/net/ethernet/netronome/nfp/nfp_app.h b/drivers/net/ethernet/netronome/nfp/nfp_app.h
index 3e9baff07100..60cb8a71e02d 100644
--- a/drivers/net/ethernet/netronome/nfp/nfp_app.h
+++ b/drivers/net/ethernet/netronome/nfp/nfp_app.h
@@ -4,10 +4,12 @@
#ifndef _NFP_APP_H
#define _NFP_APP_H 1
+#include <linux/lockdep.h>
#include <net/devlink.h>
#include <trace/events/devlink.h>
+#include "nfp_main.h"
#include "nfp_net_repr.h"
#define NFP_APP_CTRL_MTU_MAX U32_MAX
@@ -174,6 +176,13 @@ struct nfp_app {
void *priv;
};
+static inline void assert_nfp_app_locked(struct nfp_app *app)
+{
+ lockdep_assert_held(&app->pf->lock);
+}
+
+#define nfp_app_is_locked(app) lockdep_is_held(&(app)->pf->lock)
+
void nfp_check_rhashtable_empty(void *ptr, void *arg);
bool __nfp_ctrl_tx(struct nfp_net *nn, struct sk_buff *skb);
bool nfp_ctrl_tx(struct nfp_net *nn, struct sk_buff *skb);
diff --git a/drivers/net/ethernet/netronome/nfp/nfp_net_repr.c b/drivers/net/ethernet/netronome/nfp/nfp_net_repr.c
index 181ac8e789a3..ba3fa7eac98d 100644
--- a/drivers/net/ethernet/netronome/nfp/nfp_net_repr.c
+++ b/drivers/net/ethernet/netronome/nfp/nfp_net_repr.c
@@ -20,7 +20,7 @@ struct net_device *
nfp_repr_get_locked(struct nfp_app *app, struct nfp_reprs *set, unsigned int id)
{
return rcu_dereference_protected(set->reprs[id],
- lockdep_is_held(&app->pf->lock));
+ nfp_app_is_locked(app));
}
static void
@@ -476,7 +476,7 @@ nfp_reprs_clean_and_free_by_type(struct nfp_app *app, enum nfp_repr_type type)
int i;
reprs = rcu_dereference_protected(app->reprs[type],
- lockdep_is_held(&app->pf->lock));
+ nfp_app_is_locked(app));
if (!reprs)
return;
--
2.34.1
next prev parent reply other threads:[~2022-03-10 0:17 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 0:16 [RFT net-next 0/6] devlink: expose instance locking and simplify port splitting Jakub Kicinski
2022-03-10 0:16 ` [RFT net-next 1/6] devlink: expose instance locking and add locked port registering Jakub Kicinski
2022-03-10 9:14 ` Jiri Pirko
2022-03-10 20:06 ` Jakub Kicinski
2022-03-11 9:15 ` Jiri Pirko
2022-03-11 16:33 ` Jakub Kicinski
2022-03-14 12:43 ` Jiri Pirko
2022-03-11 16:09 ` Leon Romanovsky
2022-03-11 16:26 ` Jakub Kicinski
2022-03-11 16:57 ` Leon Romanovsky
2022-03-11 17:39 ` Jakub Kicinski
2022-03-11 17:41 ` Jakub Kicinski
2022-03-11 17:49 ` Leon Romanovsky
2022-03-11 18:06 ` Jakub Kicinski
2022-03-11 18:19 ` Leon Romanovsky
2022-03-10 0:16 ` Jakub Kicinski [this message]
2022-03-10 0:16 ` [RFT net-next 3/6] eth: nfp: replace driver's "pf" lock with devlink instance lock Jakub Kicinski
2022-03-10 0:16 ` [RFT net-next 4/6] eth: mlxsw: switch to explicit locking for port registration Jakub Kicinski
2022-03-10 9:17 ` Jiri Pirko
2022-03-10 20:08 ` Jakub Kicinski
2022-03-10 0:16 ` [RFT net-next 5/6] devlink: hold the instance lock in port_split / port_unsplit callbacks Jakub Kicinski
2022-03-10 0:16 ` [RFT net-next 6/6] devlink: pass devlink_port to " Jakub Kicinski
2022-03-10 8:57 ` [RFT net-next 0/6] devlink: expose instance locking and simplify port splitting Ido Schimmel
2022-03-10 21:13 ` Ido Schimmel
2022-03-10 21:28 ` Jakub Kicinski
2022-03-14 18:46 ` Jakub Kicinski
2022-03-14 19:10 ` Ido Schimmel
2022-03-14 20:11 ` Jakub Kicinski
2022-03-15 7:39 ` Leon Romanovsky
2022-03-15 15:58 ` Jakub Kicinski
2022-03-15 17:54 ` Leon Romanovsky
2022-03-10 9:05 ` Jiri Pirko
2022-03-10 9:07 ` Leon Romanovsky
2022-03-10 20:13 ` Jakub Kicinski
2022-03-11 6:30 ` Leon Romanovsky
2022-03-11 10:48 ` Simon Horman
2022-03-11 16:34 ` Jakub Kicinski
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=20220310001632.470337-3-kuba@kernel.org \
--to=kuba@kernel.org \
--cc=idosch@nvidia.com \
--cc=jiri@resnulli.us \
--cc=leonro@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=petrm@nvidia.com \
--cc=simon.horman@corigine.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).