From: Jeremy Jongepier <jeremy@autostatic.com>
To: linux-rt-users@vger.kernel.org
Subject: Re: Configuration of real-time tasks in PREEMPT_RT kernels > 2.6.33
Date: Tue, 27 Aug 2013 11:50:11 +0200 [thread overview]
Message-ID: <521C7653.9080402@autostatic.com> (raw)
In-Reply-To: <OF6C5E1E92.67FE0167-ONC1257BD3.0043D8B2-C1257BD3.00448947@br-automation.com>
[-- Attachment #1: Type: text/plain, Size: 449 bytes --]
On 08/26/2013 02:28 PM, Wolfgang Wallner wrote:
> I know that in 2.6.33 there were splitted softirqs, and that it was possible to configure each thread with its own priority.
> What are the steps that need to be done in 3.x to achieve similar results as in 2.6.33?
Isn't it still possible to configure each thread with its own priority?
Afaik IRQs still get assigned a bottom-half. I'm using rtirq myself to
prioritize softirqs.
Jeremy
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-08-27 9:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-26 12:28 Configuration of real-time tasks in PREEMPT_RT kernels > 2.6.33 Wolfgang Wallner
2013-08-27 6:17 ` SV: " Simon Falsig
2013-08-27 9:50 ` Jeremy Jongepier [this message]
2013-08-27 21:12 ` Carsten Emde
2013-08-29 7:57 ` Wolfgang Wallner
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=521C7653.9080402@autostatic.com \
--to=jeremy@autostatic.com \
--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;
as well as URLs for NNTP newsgroup(s).