From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19140 invoked by alias); 7 Aug 2007 14:02:53 -0000 Received: (qmail 18976 invoked by uid 22791); 7 Aug 2007 14:02:43 -0000 X-Spam-Check-By: sourceware.org Received: from mail.gmx.net (HELO mail.gmx.net) (213.165.64.20) by sourceware.org (qpsmtpd/0.31) with SMTP; Tue, 07 Aug 2007 14:02:36 +0000 Received: (qmail 410 invoked by uid 0); 7 Aug 2007 14:02:33 -0000 Received: from 128.131.86.182 by www093.gmx.net with HTTP; Tue, 07 Aug 2007 16:02:34 +0200 (CEST) Content-Type: text/plain; charset="iso-8859-1" Date: Tue, 07 Aug 2007 14:02:00 -0000 From: "Alois Z." Message-ID: <20070807140234.264490@gmx.net> MIME-Version: 1.0 To: ecos-discuss@ecos.sourceware.org X-Authenticated: #979605 X-Flags: 0001 X-Mailer: WWW-Mail 6100 (Global Message Exchange) Content-Transfer-Encoding: 8bit X-GMX-UID: SAGNLjoNZDIrD/vBdGY242p5emhmY4HA X-IsSubscribed: yes Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Subject: [ECOS] Thread activation disturbed by lower priority threads] X-SW-Source: 2007-08/txt/msg00032.txt.bz2 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