From: Byungchul Park <byungchul.park@lge.com>
To: paulmck@linux.vnet.ibm.com, josh@joshtriplett.org,
rostedt@goodmis.org, mathieu.desnoyers@efficios.com,
jiangshanlai@gmail.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rcu: Avoid unnecessary contention of rcu node lock
Date: Wed, 16 Nov 2016 13:49:31 +0900 [thread overview]
Message-ID: <20161116044931.GD2279@X58A-UD3R> (raw)
In-Reply-To: <1478681833-23397-1-git-send-email-byungchul.park@lge.com>
On Wed, Nov 09, 2016 at 05:57:13PM +0900, Byungchul Park wrote:
> It's unnecessary to try to print stacks of blocked tasks in the case
> that ndetected == 0. Furthermore, calling rcu_print_detail_task_stall()
> causes to acquire rnp locks as many times as the number of leaf nodes
> plus one for root node. It's unnecessary at all in the case.
Hello,
I have two questions. Could you answer them?
1. What do you think about this patch?
2. Is there a tree where patches about rcu are pulled into, before
being pulled into mainline tree?
For example, tip tree in case of scheduler patches.
It would be appriciated if you answer them.
Thank you in advance,
Byungchul
>
> Signed-off-by: Byungchul Park <byungchul.park@lge.com>
> ---
> kernel/rcu/tree.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/kernel/rcu/tree.c b/kernel/rcu/tree.c
> index 287f468..ab2f743 100644
> --- a/kernel/rcu/tree.c
> +++ b/kernel/rcu/tree.c
> @@ -1374,6 +1374,9 @@ static void print_other_cpu_stall(struct rcu_state *rsp, unsigned long gpnum)
> (long)rsp->gpnum, (long)rsp->completed, totqlen);
> if (ndetected) {
> rcu_dump_cpu_stacks(rsp);
> +
> + /* Complain about tasks blocking the grace period. */
> + rcu_print_detail_task_stall(rsp);
> } else {
> if (READ_ONCE(rsp->gpnum) != gpnum ||
> READ_ONCE(rsp->completed) == gpnum) {
> @@ -1390,9 +1393,6 @@ static void print_other_cpu_stall(struct rcu_state *rsp, unsigned long gpnum)
> }
> }
>
> - /* Complain about tasks blocking the grace period. */
> - rcu_print_detail_task_stall(rsp);
> -
> rcu_check_gp_kthread_starvation(rsp);
>
> panic_on_rcu_stall();
> --
> 1.9.1
next prev parent reply other threads:[~2016-11-16 4:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 8:57 [PATCH] rcu: Avoid unnecessary contention of rcu node lock Byungchul Park
2016-11-16 4:49 ` Byungchul Park [this message]
2016-11-16 13:59 ` Steven Rostedt
2016-11-16 19:29 ` Paul E. McKenney
2016-11-17 3:38 ` Byungchul Park
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=20161116044931.GD2279@X58A-UD3R \
--to=byungchul.park@lge.com \
--cc=jiangshanlai@gmail.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rostedt@goodmis.org \
/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