From: Thomas Gleixner <tglx@linutronix.de>
To: Tim Sander <tim.sander@hbm.com>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: RT Throtteling with PREEMT-RT on UBIFS root fs update
Date: Thu, 17 Nov 2011 15:15:16 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.02.1111171511260.4902@ionos> (raw)
In-Reply-To: <201111171454.18742.tim.sander@hbm.com>
On Thu, 17 Nov 2011, Tim Sander wrote:
> Well it can be said that it is not ksoftirqd/0 going berserk which is
> triggering this. So i guess when this message is printed it just shows that
> the cpu had been temporarily overloded with work in interrupt context.
> Is there more harm to expect from this message or save to ignore if the
> systemload is normal again?
There is no harm, this message is informative and if that behaviour is
directly related to an ubifs update then I'd say we should not worry
too much about it. Though it'd be interesting to poke the UBIFS folks
about it.
Thanks,
tglx
prev parent reply other threads:[~2011-11-17 14:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-11 9:56 RT Throtteling with PREEMT-RT on UBIFS root fs update Tim Sander
2011-11-17 13:54 ` Tim Sander
2011-11-17 14:15 ` Thomas Gleixner [this message]
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=alpine.LFD.2.02.1111171511260.4902@ionos \
--to=tglx@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=tim.sander@hbm.com \
/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;
as well as URLs for NNTP newsgroup(s).