linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Grant Edwards <grant.b.edwards@gmail.com>
To: Remy Bohmer <linux@bohmer.net>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: Using patch-2.6.33.7.2-rt30 increases latency and CPU usage?
Date: Thu, 10 May 2012 08:53:20 -0500	[thread overview]
Message-ID: <20120510135320.GA9568@grante> (raw)
In-Reply-To: <CANqCtQJsr6xV9aU5LbXuOOtYTvcHT6113cy0+6smKBtZAdcRGA@mail.gmail.com>

On Thu, May 10, 2012 at 11:46:26AM +0200, Remy Bohmer wrote:
> 2012/5/10 Grant Edwards <grant.b.edwards@gmail.com>:
>
>> Unfortunately, the requirements are a bit fuzzy -- I've got an ISR
>> deadline of about 20us that I'm trying to meet [I wouldn't mind a
>> little chat with the person who designed _that_ requirement into the
>> hardware].  What I don't know is how hard that deadline is.  With the
>> RT patch (and without IRQF_NODELAY), I miss the deadline most of the
>> time (I'd guess about 80% of the time).
> 
> Given my experience with these cores and the RT patch: This 20usec is
> too close.

That's pretty much what I've decided.

> There are some places in the code that have interrupt disable section
> of about 30usec (also process ctx-switch cache flush have high
> impact)
>
> So, I expect you will not get this very robust.
>
> If the 20usec requirement is hard, you can also look at using an FIQ.

Does the normal AT91 kernel not use FIQs at all?  If so, I might be
able to dedicate the FIQ to this function and have it happen without
the Linux kernel knowing about it (or affecting it).  Any
communication between it and a normal user-task would have to be
handled carefully...

-- 
Grant
--
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

  reply	other threads:[~2012-05-10 13:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-09 21:18 Using patch-2.6.33.7.2-rt30 increases latency and CPU usage? Grant Edwards
2012-05-09 22:00 ` Grant Edwards
2012-05-09 22:13   ` Joachim Achtzehnter
2012-05-09 23:18     ` Grant Edwards
2012-05-10  9:46       ` Remy Bohmer
2012-05-10 13:53         ` Grant Edwards [this message]
2012-05-11 13:42           ` Remy Bohmer
2012-05-11 13:56             ` Grant Edwards
2012-05-11 18:46               ` Tim Sander
2012-05-15 17:33       ` Steven Rostedt
2012-05-15 22:58         ` Grant Edwards
2012-05-15 23:06           ` Steven Rostedt

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=20120510135320.GA9568@grante \
    --to=grant.b.edwards@gmail.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=linux@bohmer.net \
    /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).