public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Alois Z." <alois@gmx.at>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] Thread activation disturbed by lower priority threads]
Date: Tue, 07 Aug 2007 14:02:00 -0000	[thread overview]
Message-ID: <20070807140234.264490@gmx.net> (raw)

Hi, 

as I got no response to me questions (see below) I may have to add a few things for clarification.

First of all I'm running an an AT91M5580A processor (thy phytec board). I changed the ecos settings so that the timer tick is now 1ms. The reason for this is that I need such a small tick for my application. Does this anyhow influence the scheduling algorithm. Are there settings that need to be adjusted appart from denominator, nominator and timesclice value?

I did more measurements and found out that the timer DSR is really stable. even more stable than on some other systems (non ecos) I'm using. The problem is that the time between posting on the semaphore (the thread is waiting on) until the thread starts executing  is varying largly. It seems that it is prolonged by other execution elements. And this even when the thread under question is the thread with the highest priority.

would be great if this clearifies my problem a little bit more.

Thanks,
Alois

Hi,

In a larger project I have a problem when doing a timed activation of threads.

In the timer alarm handler I check if any thread is ready for activation and post on a semaphore the thread is waiting for.

This works fine when I have only one or two such timed threads the activation jitter of the thread (i.e. the jitter when the threads starts its execution) is ok. But when I add more threads this jitter grows tremendously. Each thread has an own priority. And event the thread with with the highest priority (in my case 2) has this large jitter (more than half of the cycle time).

Is there a way to improve the behavior of the activation. Do I the timed activation the wrong way. Can I improve the timing behavior of the scheduler through the real-time clock settings.

By the way I use the multilevel scheduler.

Thanks,
Alois



-- 
Psssst! Schon vom neuen GMX MultiMessenger gehört?
Der kanns mit allen: http://www.gmx.net/de/go/multimessenger

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

             reply	other threads:[~2007-08-07 14:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-07 14:02 Alois Z. [this message]
2007-08-07 14:41 ` Andrew Lunn
2007-08-07 17:35   ` Paul D. DeRocco
2007-08-07 18:55     ` Andrew Lunn
     [not found]   ` <20070808075810.250840@gmx.net>
2007-08-08  8:10     ` Andrew Lunn
2007-08-16 20:05       ` Alois Zoitl
2007-08-16 20:22         ` Andrew Lunn
     [not found]           ` <20070817072849.22110@gmx.net>
2007-08-17  8:08             ` Andrew Lunn
2007-08-17  7:34 Alois Z.
2007-08-17  8:08 ` Pieter-Jan Busschaert
2007-08-17  8:14   ` Andrew Lunn
2007-08-17  8:46     ` Pieter-Jan Busschaert
2007-08-17  8:59       ` Andrew Lunn
2007-08-23 20:38   ` Alois Zoitl

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=20070807140234.264490@gmx.net \
    --to=alois@gmx.at \
    --cc=ecos-discuss@ecos.sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).