Martin Mokrejs wrote:
>>>> Nope, you get that message once to tell you that we throttle RT tasks. >>> >>> I think the message could improved to explain this is a warn ONCE message >>> and >>> that there is no "[sched_delayed] sched: RT throttling deactivated" >>> counterpart >>> message to be anticipated. >> >> Would something like: >> >> sched: [ONCE] RT throttle hit -- inspect system configuration. >> >> Be a better message? > > Not really. I would prefer something like: > > [sched_delayed] sched: stopped running $cmd on CPU%d in favor of RR/FIFO task > $psname Actually, to retain the message text appearing in current kernel so that people can find by e.g. Google newer syntax and possibly this thread maybe much better would be: [sched_delayed] sched: RT throttling limit $d hit. Stopped running $cmd on CPU%d in favor of RR/FIFO task $psname. Will not issue any more these messages until reboot. I know, looong line. I just realized this is about some threshold limit value, and you mean that iwlwifi contributed the highest increase compared to the other kernel threads on my system. sysctl -q -a | grep -i limit does not show what is the actual value. Am probably looking into a wrong place. ;-) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
