From: Alois Zoitl <alois@gmx.at>
To: eCos Disuss <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Thread activation disturbed by lower priority threads]
Date: Thu, 16 Aug 2007 20:05:00 -0000 [thread overview]
Message-ID: <46C4ADE6.9080101@gmx.at> (raw)
In-Reply-To: <20070808081015.GB29246@lunn.ch>
Hi,
thanks you definitely pointed me into the right direction. The problem
is located with the mutexes. I removed all mutexes in questions and set
my timing measurement points directly after the semaphore that is in
charge of activating my threads.After making more measurements and
playing a little bit around I found it that when I set the priority
inversion protocol to none (using cyg_mutex_set_protocol). The timing is
as expected. So I thought it could be that before I was using priority
ceiling which would be an explanation for the delay as every time a
mutex is gathered the thread will get priorty 0. So I changed to
priority inheritance. This from my point of view should do the job as I
like to have it done.
But when using priority inheritance I get the same bad timing as in the
beginning.
And as longer I think I don't know why the tread activation of the
highest priority thread is prolonged by threads holding a mutex with
priority inheritance where each of the treads that my also get this
mutex has a lower priority. So I'm completly confuesed. Any Ideas what
could be the problem or what I could do?
For my current tests no priority inversion protocol is just fine, but
for further more complected tests I think i will need something like
priority inheritance so it would be nice to have it.
Thanks,
Alois
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2007-08-16 20:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-07 14:02 Alois Z.
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 [this message]
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=46C4ADE6.9080101@gmx.at \
--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).