[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20221016162305.2489629-13-joel@joelfernandes.org>
Date: Sun, 16 Oct 2022 16:23:04 +0000
From: "Joel Fernandes (Google)" <joel@...lfernandes.org>
To: rcu@...r.kernel.org
Cc: linux-kernel@...r.kernel.org, frederic@...nel.org,
paulmck@...nel.org,
"Joel Fernandes (Google)" <joel@...lfernandes.org>
Subject: [PATCH v9 12/13] rxrpc: Use call_rcu_flush() instead of call_rcu()
call_rcu() changes to save power may cause slowness. Use the
call_rcu_flush() API instead which reverts to the old behavior.
We find this via inspection that the RCU callback does a wakeup of a
thread. This usually indicates that something is waiting on it. To be
safe, let us use call_rcu_flush() here instead.
Signed-off-by: Joel Fernandes (Google) <joel@...lfernandes.org>
---
net/rxrpc/conn_object.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/rxrpc/conn_object.c b/net/rxrpc/conn_object.c
index 22089e37e97f..fdcfb509cc44 100644
--- a/net/rxrpc/conn_object.c
+++ b/net/rxrpc/conn_object.c
@@ -253,7 +253,7 @@ void rxrpc_kill_connection(struct rxrpc_connection *conn)
* must carry a ref on the connection to prevent us getting here whilst
* it is queued or running.
*/
- call_rcu(&conn->rcu, rxrpc_destroy_connection);
+ call_rcu_flush(&conn->rcu, rxrpc_destroy_connection);
}
/*
--
2.38.0.413.g74048e4d9e-goog
Powered by blists - more mailing lists