From: Tim Sander <tim@krieglstein.org>
To: linux-rt-users@vger.kernel.org
Subject: 100% RT load on 2 processor SMP machine
Date: Mon, 15 Oct 2018 17:44:42 +0200 [thread overview]
Message-ID: <2762823.FS3CZOEJbg@dabox> (raw)
Hi
I just disovered a bug in my playground realtime application which led to 100%
load on one core. This was the non normal case when the system was waiting for
a network client to connect and i had a fifo buffer overflow which led
accidentially to a busy wait loop with 98 fifo priority. This in turn lead to
a system which did not accept any new network connections.
The expected behaviour for a SMP system which still has one processor lightly
loaded should be that it still works "normal" even if one core is overloaded
with hard realtime work. Are there any explanations for this behavior?
The embedded system im am using is an pretty dated Intel/Altera Cortex A9.
Best regards
Tim
next reply other threads:[~2018-10-15 23:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-15 15:44 Tim Sander [this message]
2018-10-23 9:36 ` 100% RT load on 2 processor SMP machine Sebastian Andrzej Siewior
2018-10-25 9:56 ` Tim Sander
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=2762823.FS3CZOEJbg@dabox \
--to=tim@krieglstein.org \
--cc=linux-rt-users@vger.kernel.org \
/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