From: Neeraj Upadhyay <neeraju@codeaurora.org>
To: paulmck@linux.vnet.ibm.com
Cc: josh@joshtriplett.org, rostedt@goodmis.org,
mathieu.desnoyers@efficios.com, jiangshanlai@gmail.com,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Query regarding srcu_funnel_exp_start()
Date: Fri, 27 Oct 2017 22:15:04 +0530 [thread overview]
Message-ID: <946852c9-88cb-7363-e74d-82a1efbd3be1@codeaurora.org> (raw)
In-Reply-To: <20171027122601.GJ3659@linux.vnet.ibm.com>
On 10/27/2017 05:56 PM, Paul E. McKenney wrote:
> On Fri, Oct 27, 2017 at 02:23:07PM +0530, Neeraj Upadhyay wrote:
>> Hi,
>>
>> One query regarding srcu_funnel_exp_start() function in
>> kernel/rcu/srcutree.c.
>>
>> static void srcu_funnel_exp_start(struct srcu_struct *sp, struct
>> srcu_node *snp,
>> unsigned long s)
>> {
>> <snip>
>> if (!ULONG_CMP_LT(sp->srcu_gp_seq_needed_exp, s))
>> sp->srcu_gp_seq_needed_exp = s;
>> <snip>
>> }
>>
>> Why is sp->srcu_gp_seq_needed_exp set to 's' if srcu_gp_seq_needed_exp is >=
>> 's'. Shouldn't srcu_gp_seq_needed_exp be equal to the greater of both?
>
> Let's suppose that it is incorrect as currently written. Can you
> construct a test case demonstrating a failure of some sort, then provide
> a fix?
Will check this. Might take some time to build a test case.
>
> To start with, if it is currently incorrect, what would be the nature
> of the failure?
>
> Thanx, Paul
>
Hi Paul,
I see below scenario, where new gp won't be expedited. Please correct
me if I am missing something here.
1. CPU0 calls synchronize_srcu_expedited()
synchronize_srcu_expedited()
__synchronize_srcu()
__call_srcu()
s = rcu_seq_snap(&sp->srcu_gp_seq); // lets say srcu_gp_seq
= 0;
// s = 0x100
sdp->srcu_gp_seq_needed = s // 0x100
needgp = true
sdp->srcu_gp_seq_needed_exp = s // 0x100
srcu_funnel_gp_start()
sp->srcu_gp_seq_needed_exp = s;
srcu_gp_start(sp);
rcu_seq_start(&sp->srcu_gp_seq);
2. CPU1 calls normal synchronize_srcu()
synchronize_srcu()
__synchronize_srcu(sp, true)
__call_srcu()
s = rcu_seq_snap(&sp->srcu_gp_seq); // srcu_gp_seq = 1
// s= 0x200
sdp->srcu_gp_seq_needed = s; // 0x200
srcu_funnel_gp_start()
smp_store_release(&sp->srcu_gp_seq_needed, s); // 0x200
3. CPU3 calls synchronize_srcu_expedited()
synchronize_srcu_expedited()
__synchronize_srcu()
__call_srcu()
s = rcu_seq_snap(&sp->srcu_gp_seq); // srcu_gp_seq = 1
// s = 0x200
sdp->srcu_gp_seq_needed_exp = s // 0x200
srcu_funnel_exp_start(sp, sdp->mynode, s);
// sp->srcu_gp_seq_needed_exp = 0x100
// s = 0x200 ; sp->srcu_gp_seq_needed_exp is not updated
if (!ULONG_CMP_LT(sp->srcu_gp_seq_needed_exp, s))
sp->srcu_gp_seq_needed_exp = s;
Thanks
Neeraj
--
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a
member of the Code Aurora Forum, hosted by The Linux Foundation
next prev parent reply other threads:[~2017-10-27 16:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-27 8:53 Neeraj Upadhyay
2017-10-27 12:26 ` Paul E. McKenney
2017-10-27 16:45 ` Neeraj Upadhyay [this message]
2017-10-27 22:20 ` Paul E. McKenney
2017-10-28 3:49 ` Neeraj Upadhyay
2017-10-29 19:24 ` Paul E. McKenney
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=946852c9-88cb-7363-e74d-82a1efbd3be1@codeaurora.org \
--to=neeraju@codeaurora.org \
--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
all inboxes | Powered by JetHome®