From: Martin Mokrejs <mmokrejs@fold.natur.cuni.cz>
To: Martin Mokrejs <mmokrejs@fold.natur.cuni.cz>,
Peter Zijlstra <peterz@infradead.org>
Cc: Theodore Tso <tytso@mit.edu>,
Thomas Gleixner <tglx@linutronix.de>,
mingo@redhat.com, LKML <linux-kernel@vger.kernel.org>,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [sched_delayed] sched: RT throttling activated
Date: Fri, 23 Aug 2013 15:01:57 +0200 [thread overview]
Message-ID: <52175D45.4010506@fold.natur.cuni.cz> (raw)
In-Reply-To: <5217599C.3080707@fold.natur.cuni.cz>
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. ;-)
next prev parent reply other threads:[~2013-08-23 13:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-23 8:53 Martin Mokrejs
2013-08-23 10:09 ` Peter Zijlstra
2013-08-23 10:38 ` Martin Mokrejs
2013-08-23 11:02 ` Peter Zijlstra
2013-08-23 11:35 ` Martin Mokrejs
2013-08-23 12:10 ` Peter Zijlstra
2013-08-23 12:33 ` Johannes Berg
2013-08-23 13:06 ` Peter Zijlstra
2013-08-23 13:10 ` Johannes Berg
2013-08-23 12:46 ` Martin Mokrejs
2013-08-23 13:01 ` Martin Mokrejs [this message]
2013-08-23 19:07 ` Martin Mokrejs
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=52175D45.4010506@fold.natur.cuni.cz \
--to=mmokrejs@fold.natur.cuni.cz \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=tytso@mit.edu \
/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®