From: riel@surriel.com (Rik van Riel)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Kernel schedules kernel tasks on isolated cpus, SCHED_FIFO prevents kernel tasks from running
Date: Wed, 28 Jun 2017 17:18:54 -0400 [thread overview]
Message-ID: <1498684734.20270.127.camel@surriel.com> (raw)
In-Reply-To: <4d6a442c-ea18-42c3-0865-63e2c12338d8@charlesworthresearch.com>
On Wed, 2017-06-28 at 08:39 -0500, Andrei Hurynovich wrote:
> Hi.
>
> We are trying to build realtime(-ish) system based on rhel6(kernel?
> 2.6.32-642.1.1.el6.x86_64).
>
> We used isolcpus to remove some cpus from process?
> scheduling(isolcpus=2-19 nohz_full=2-19 rcu_nocbs=2-19).
>
> We spin off a program thread that set's its cpu affinity to one of
> those?
> isolated cpus, sets its scheduling chass to SCHED_FIFO, spins in a
> loop?
> and never sched_yield()-s to the kernel.
>
> We set sysctl kernel.sched_rt_runtime_us = -1 so realtime threads
> are?
> NEVER interrupted.
You want an actual realtime kernel for that to work
right. The real time kernel currently supported by
Red Hat is 3.10 based, not 2.6.32 based.
--
All rights reversed
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 473 bytes
Desc: This is a digitally signed message part
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20170628/f1a5fb2a/attachment.bin
prev parent reply other threads:[~2017-06-28 21:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 13:39 Kernel schedules kernel tasks on isolated cpus, SCHED_FIFO prevents kernel tasks from running Andrei Hurynovich
2017-06-28 18:04 ` valdis.kletnieks at vt.edu
2017-06-28 19:02 ` Andrei Hurynovich
2017-06-28 20:49 ` valdis.kletnieks at vt.edu
2017-06-28 18:27 ` Greg KH
2017-06-28 21:18 ` Rik van Riel [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=1498684734.20270.127.camel@surriel.com \
--to=riel@surriel.com \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).