From: Raphael Hertzog <raphael@ouaza.com>
To: linux-rt-users@vger.kernel.org
Subject: Changing real time priority of interrupt handler thread
Date: Wed, 5 May 2010 15:08:45 +0200 [thread overview]
Message-ID: <20100505130845.GA9118@rivendell> (raw)
[ Please cc me on answer, I'm not subscribed to the list, I tried to ask
this question on the #linux-rt channel but got no answers so I try on the
list ]
Hello,
with 2.6.33.2-rt13 the IRQ handler thread for serial devices is
no longer persistent after its creation. Up to now I had a startup
script opening the serial device in order to create the IRQ handler
thread that would run chrt on $(pidof IRQ-4) and the setting would be
persistent until next reboot.
This is no longer possible, I would have to run chrt every time that I
open the serial port and I would like to avoid modifying all my
applications to do this.
Is there any other alternative like making the thread persistent with some
options (/sys or /proc tuning)?
Or is there a kernel config option for this ?
In case it was not clear, I want to run the IRQ handler of the serial
ports at a higher priority than the other ones (like network, disk,
etc.) to avoid buffer overruns.
Cheers,
--
Raphaël Hertzog -+- http://www.ouaza.com
Freexian : des développeurs Debian au service des entreprises
http://www.freexian.com
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2010-05-05 13:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 13:08 Raphael Hertzog [this message]
2010-05-05 18:37 ` Changing real time priority of interrupt handler thread Nivedita Singhvi
2010-05-06 17:54 ` Steven Rostedt
2010-05-18 14:28 ` Darcy L. Watkins
2010-05-18 15:04 ` Nivedita Singhvi
2010-05-18 15:17 ` Darcy L. Watkins
2010-05-18 15:24 ` Nivedita Singhvi
2010-05-25 13:02 ` Raphael Hertzog
2010-05-25 13:25 ` Steven Rostedt
2010-05-25 13:50 ` Clark Williams
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=20100505130845.GA9118@rivendell \
--to=raphael@ouaza.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).