RCU stall warnings even with rcu_nocbs and rcu_nocb_poll

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

 



Hello,

I'm trying to isolate some cores to run a CPU-bound real-time task and
even though I'm using rcu_nocbs and rcu_nocb_poll, I can see the rcuc
threads wake up, and I get RCU stall warnings on the isolated core.
As per the documentation, if I use rcutree.kthread_prio with a
priority > my RT task, then the rcu stall does not happen.

However I find it confusing: why are the rcuc threads woken up on the
isolated cores despite using rcu_nocbs and rcu_nocb_poll? In my (very
likely erroneous) understanding, I shouldn't have to fiddle with rcu
priority... In other words, how come I get rcu stalls on cores that
have no rcu callbacks?

Thanks.



[Index of Archives]     [RT Stable]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux