All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nivedita Singhvi <niv@us.ibm.com>
To: "Darcy L. Watkins" <dwatkins@tranzeo.com>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: Changing real time priority of interrupt handler thread
Date: Tue, 18 May 2010 08:04:58 -0700	[thread overview]
Message-ID: <4BF2AC9A.3060301@us.ibm.com> (raw)
In-Reply-To: <1274192889.17960.14.camel@localhost.localdomain>

Darcy L. Watkins wrote:

>>> Have you tried using the rtctl utility and the /etc/rtgroups file?
> 
> Where are the source tarball projects for these located so I can try
> porting/using them [at least some of it] on my embedded linux?  ... or
> is this a proprietary Redhat utility only in RPM binaries?  Google
> search seems to mainly land me at IBM and Redhat user docs and FAQs.

rtctl is GPL, not proprietary. A quick google search brought
up the following:

http://ftp.riken.go.jp/pub/Linux/cern/mrg/slc5X/SRPMS/

http://ftp.riken.go.jp/pub/Linux/cern/mrg/slc5X/SRPMS/rtctl-1.7-1.el5rt.src.rpm

> Perhaps my issue earlier with serial buffer overruns is just a tune up
> issue.
> 
> I want to tune up RT on PowerPC 405 and ARM11 MX.31 based embedded
> systems where the rootfs is built (cross compiled) using
> buildroot/uclibc, etc and not x86 binaries from a full feature distro
> such as Fedora, Debian, etc.

Setting thread priorities for your environment will certainly
be a good thing in general.

thanks,
Nivedita

  reply	other threads:[~2010-05-18 15:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-05 13:08 Changing real time priority of interrupt handler thread Raphael Hertzog
2010-05-05 18:37 ` Nivedita Singhvi
2010-05-06 17:54   ` Steven Rostedt
2010-05-18 14:28     ` Darcy L. Watkins
2010-05-18 15:04       ` Nivedita Singhvi [this message]
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=4BF2AC9A.3060301@us.ibm.com \
    --to=niv@us.ibm.com \
    --cc=dwatkins@tranzeo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.