From: greg@kroah.com (Greg KH)
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 20:27:23 +0200 [thread overview]
Message-ID: <20170628182723.GA29354@kroah.com> (raw)
In-Reply-To: <4d6a442c-ea18-42c3-0865-63e2c12338d8@charlesworthresearch.com>
On Wed, Jun 28, 2017 at 08:39:07AM -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).
Wow, you do realize that is a _very_ old and obsolete kernel, supported
by no one except Red Hat. If you stick with it, you are going to have
to get your support from them, not the community, as you are already
paying for it :)
Good luck!
greg k-h
next prev parent reply other threads:[~2017-06-28 18:27 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 [this message]
2017-06-28 21:18 ` Rik van Riel
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=20170628182723.GA29354@kroah.com \
--to=greg@kroah.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).