From: Nivedita Singhvi <niv@us.ibm.com>
To: David L <idht4n@gmail.com>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: idle task starvation with rt patch
Date: Wed, 06 May 2009 14:04:30 -0700 [thread overview]
Message-ID: <4A01FB5E.1000006@us.ibm.com> (raw)
In-Reply-To: <b79371120905061247o72198a1ak6b4527ebfb60098a@mail.gmail.com>
David L wrote:
> Hi,
>
> I'm a newbie trying to see if the rt patch will improve
> the performance of a PPC Linux receiver. We need
> to read data from an FGPA correlator about every msec
> although we can tolerate 5-10 msecs from time to time.
>
> Without the real-time patches, we find that we sometimes
> miss our timing deadlines especially when we have multiple
> processes with "real-time" (SCHED_FIFO) threads. I tried
I take it you weren't seeing crashes on mainline?
> to use the 2.6.29.2-rt11 patch to see if it helped, but things
> got much worse. We have about 30-60 percent idle CPU
> without the patches... after applying the patches, I found
> that we had essentially no idle time. Below are excepts
> from the kernel sched_switch trace file while our process
> is running with and without the real-time patches applied.
What priority are you running your real time tasks at?
> I notice there are IRQ-related processes with the real-time
> patches that don't exist in without the patches. But the main
> thing to notice is that there is no idle time which eventually
> causes the process to crash because low priority threads
Which process crashed?
> are starved for too long. Am I doing something wrong or
> is it expected overhead of the real-time patches will cause
> problems like this under this kind of interrupt load?
Making sure your priorities are set right so you don't
starve essential processes is important...rt makes it
easy to shoot yourself in the foot...
thanks,
Nivedita
next prev parent reply other threads:[~2009-05-06 21:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-06 19:47 idle task starvation with rt patch David L
2009-05-06 21:04 ` Nivedita Singhvi [this message]
2009-05-06 22:19 ` David L
2009-05-06 23:18 ` Nivedita Singhvi
2009-05-07 5:29 ` Sujit Karataparambil
2009-05-07 13:01 ` David L
2009-05-07 13:15 ` Sujit Karataparambil
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=4A01FB5E.1000006@us.ibm.com \
--to=niv@us.ibm.com \
--cc=idht4n@gmail.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).