Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Qiuxu Zhuo <qiuxu.zhuo@intel.com>
To:     paulmck@kernel.org
Cc:     dave@stgolabs.net, frederic@kernel.org, jiangshanlai@gmail.com,
        joel@joelfernandes.org, josh@joshtriplett.org,
        linux-kernel@vger.kernel.org, mathieu.desnoyers@efficios.com,
        qiuxu.zhuo@intel.com, quic_neeraju@quicinc.com,
        rcu@vger.kernel.org, rostedt@goodmis.org
Subject: [PATCH v4 0/2] Stop kfree_scale_thread thread(s) after unloading rcuscale
Date:   Wed, 22 Mar 2023 19:42:39 +0800
Message-Id: <20230322114241.88118-1-qiuxu.zhuo@intel.com>
In-Reply-To: <a4a3e103-78b3-4be3-80b8-bbae7b1bb2f4@paulmck-laptop>
References: <a4a3e103-78b3-4be3-80b8-bbae7b1bb2f4@paulmck-laptop>
Precedence: bulk

v1 -> v2:

 - Move rcu_scale_cleanup() after kfree_scale_cleanup() to eliminate the
   declaration of kfree_scale_cleanup().

 - Remove the unnecessary step "modprobe torture" from the commit message.

 - Add the description for why move rcu_scale_cleanup() after
   kfree_scale_cleanup() to the commit message.

v2 -> v3:

 - Split the single v2 patch into two patches.

 - Move the commit message description for why move rcu_scale_cleanup()
   after kfree_scale_cleanup() to Patch 1.

v3 -> v4 (No function changes):

 - Rebased Patch 1 & 2 on top of the rcu "-dev" branch.

 - Added two "Reviewed-by" tags to the commit message of Patch 2.


Qiuxu Zhuo (2):
  rcu/rcuscale: Move rcu_scale_*() after kfree_scale_cleanup()
  rcu/rcuscale: Stop kfree_scale_thread thread(s) after unloading rcuscale

 kernel/rcu/rcuscale.c | 199 ++++++++++++++++++++++--------------------
 1 file changed, 102 insertions(+), 97 deletions(-)


base-commit: 86b3da94693e412ca43d996a7e6ed5766ef7a5f4
-- 
2.17.1