A small question about rcu_nocb_wait_contended

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Dear RCUers:

When I study the function rcu_nocb_try_bypass, the only place it can
be called is from
function __call_rcu_common, and __call_rcu_common disable irq before
call rcu_nocb_try_bypass, so, I assume when we enter
rcu_nocb_try_bypass, there will be no
context switch.

In rcu_nocb_try_bypass, rcu_nocb_wait_contended got called, the
purpose of rcu_nocb_wait_contended is "relying on the fact that at
most two kthreads and one CPU contend for this lock".

My question is: assume there will be no context switch, why will there
be two kthreads competing for this CPU lock?

I have stumbled on this question for more than a year.

Thank you all in advance ;-)

Best Regard
Zhouyi



[Index of Archives]     [Linux Samsung SoC]     [Linux Rockchip SoC]     [Linux Actions SoC]     [Linux for Synopsys ARC Processors]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]


  Powered by Linux