linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dennis Borgmann <dennis.borgmann@googlemail.com>
To: linux-rt-users@vger.kernel.org
Subject: [Linux-RT]High CPU-load due to IRQ servicing
Date: Thu, 23 Dec 2010 15:28:48 +0100	[thread overview]
Message-ID: <4D135CA0.9020900@googlemail.com> (raw)

Hello linux-rt list!

I am using the RT-patchset with a 2.6.33.7-Kernel on a PCEngines
ALIX-Board (AMD Geode 500MHz). In several prior projects, everything
worked fine.

Right now, I am reading four virtual USB ports in parallel
(/dev/ttyUSB0-3) using an own single-threaded program for this. Data is
coming in on each port in intervals as fast as 40ms, each ~550 bytes, at
250.000 BAUD.

The problem I can observe is, that sometimes the CPU load goes up to
100% regarding the servicing of hardware IRQs.

I know, since I observed this via top(1). There is 100% on "hi" for a
some amount of time(<0.5s). Using a program called "itop", I was able to
check the interrupts per second and each time, the CPU gets this high
load, I observe about 1500 interrupts per second on IRQ 0 ("timer").

The result of this is, that my program is frozen for about 300ms, which
destroys the purpose of my software. In addition, the program stops
receiving data from all the four virtual USB ports, but only gets data
from one or two of the ports. So from this point on my program is broken
due to failure within the linux system.

First of all: What could I be doing wrong?
Second: Could this be a real-time bug? Or a bug within the driver I am
using (ftdi.c on FT4232H)?
Third: Could anyone image an improvement by making the software multi
threaded? One thread for each USB-port?

Kind regards for every hint about my problem.
Dennis

                 reply	other threads:[~2010-12-23 14:28 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4D135CA0.9020900@googlemail.com \
    --to=dennis.borgmann@googlemail.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).