From: Julian Anastasov <ja@ssi.bg>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Simon Horman <horms@verge.net.au>,
Eric Dumazet <eric.dumazet@gmail.com>,
Ingo Molnar <mingo@redhat.com>,
lvs-devel@vger.kernel.org, netdev@vger.kernel.org,
netfilter-devel@vger.kernel.org, linux-kernel@vger.kernel.org,
Pablo Neira Ayuso <pablo@netfilter.org>,
Dipankar Sarma <dipankar@in.ibm.com>
Subject: Re: [PATCH v2 1/2] sched: Add cond_resched_rcu_lock() helper
Date: Thu, 2 May 2013 22:24:55 +0300 (EEST) [thread overview]
Message-ID: <alpine.LFD.2.00.1305022211420.25417@ja.ssi.bg> (raw)
In-Reply-To: <alpine.LFD.2.00.1305022140020.31548@ja.ssi.bg>
Hello,
On Thu, 2 May 2013, Julian Anastasov wrote:
> Note that I'm testing on some 9-year old
> UP system, i.e. 1 CPU. Now I enabled SMP to test CONFIG_TREE_RCU
> and the results are same. I think, it should be just like
> the TINY_RCU in terms of these debuggings (non-preempt). Extra
> rcu_read_lock gives me "Illegal context switch in RCU read-side
> critical section" in addition to the "BUG: sleeping function
> called from invalid context" message.
Just to clarify about the test with extra
rcu_read_lock because above paragraph is very confusing:
- The __might_sleep call with PREEMPT_ACTIVE | PREEMPT_RCU_OFFSET
just warns with "BUG: sleeping function called from invalid context"
because its rcu_sleep_check is silenced. We match the
nesting depth only.
- but __cond_resched -> __schedule -> schedule_debug warns about
the extra rcu_read_lock() with "BUG: scheduling while atomic" and
then with "Illegal context switch in RCU read-side critical section"
from rcu_sleep_check(0).
Regards
--
Julian Anastasov <ja@ssi.bg>
next prev parent reply other threads:[~2013-05-02 19:24 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-30 2:52 [PATCH v2 0/2] " Simon Horman
2013-04-30 2:52 ` [PATCH v2 1/2] " Simon Horman
2013-04-30 7:12 ` Julian Anastasov
2013-04-30 7:29 ` Simon Horman
2013-04-30 7:52 ` Julian Anastasov
2013-05-01 9:10 ` Peter Zijlstra
2013-05-01 12:46 ` Paul E. McKenney
2013-05-01 14:32 ` Paul E. McKenney
2013-05-02 7:27 ` Peter Zijlstra
2013-05-01 15:17 ` Peter Zijlstra
2013-05-01 15:29 ` Eric Dumazet
2013-05-01 15:59 ` Peter Zijlstra
2013-05-01 16:02 ` Paul E. McKenney
2013-05-01 16:57 ` Peter Zijlstra
2013-05-01 17:30 ` Paul E. McKenney
2013-05-01 14:22 ` Julian Anastasov
2013-05-01 15:55 ` Peter Zijlstra
2013-05-01 18:22 ` Julian Anastasov
2013-05-01 19:04 ` Paul E. McKenney
2013-05-02 7:26 ` Peter Zijlstra
2013-05-02 10:06 ` Julian Anastasov
2013-05-02 15:54 ` Julian Anastasov
2013-05-02 17:32 ` Paul E. McKenney
2013-05-02 18:55 ` Julian Anastasov
2013-05-02 19:24 ` Julian Anastasov [this message]
2013-05-02 19:34 ` Paul E. McKenney
2013-05-02 20:19 ` Julian Anastasov
2013-05-02 22:31 ` Paul E. McKenney
2013-05-03 7:52 ` Julian Anastasov
2013-05-03 16:30 ` Paul E. McKenney
2013-05-03 17:04 ` Peter Zijlstra
2013-05-03 17:34 ` Paul E. McKenney
2013-05-03 18:09 ` Peter Zijlstra
2013-05-03 17:47 ` Julian Anastasov
2013-05-04 7:23 ` Julian Anastasov
2013-05-04 18:03 ` Paul E. McKenney
2013-04-30 2:52 ` [PATCH v2 2/2] ipvs: Use cond_resched_rcu_lock() helper when dumping connections Simon Horman
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=alpine.LFD.2.00.1305022211420.25417@ja.ssi.bg \
--to=ja@ssi.bg \
--cc=dipankar@in.ibm.com \
--cc=eric.dumazet@gmail.com \
--cc=horms@verge.net.au \
--cc=linux-kernel@vger.kernel.org \
--cc=lvs-devel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.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®