* Brian Silverman | 2015-03-09 20:36:27 [-0400]:
>> It looks like your softirq for net_rx is getting a packet and then after
>> raising NET_RX (again?) it blocks on a lock. In order to get this lock
>> it boosts and schedules bash. It gets runable but on the other CPU. On
>> CPU1 there is nothig g
On Mon, Mar 9, 2015 at 12:08 PM, Sebastian Andrzej Siewior
wrote:
> * Brian Silverman | 2015-03-05 00:16:20 [-0500]:
>
>>Beforehand, 000 is spending most of its time in interrupts, but bash
>>is doing something related to memory management on it in between.
>>bash-14721 [000] ..1
* Brian Silverman | 2015-03-05 00:16:20 [-0500]:
>Beforehand, 000 is spending most of its time in interrupts, but bash
>is doing something related to memory management on it in between.
>bash-14721 [000] ..1 6854.629126: rt_spin_lock
> <-free_pcppages_bulk
>bash-14721
Hi,
I'm seeing "NOHZ: local_softirq_pending" warnings with 3.14.31-rt28
(3.14.3-rt4 too). They're mostly "NOHZ: local_softirq_pending 08"
(NET_RX) but they happen occasionally for other softirqs too (0c aka
NET_RX and NET_TX is second-most common). CONFIG_PREEMPT_RT_FULL and
CONFIG_NO_HZ_FULL(_ALL
4 matches
Mail list logo