From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: "Thomas, Brieuc (GE Healthcare)" <Brieuc.Thomas@domain.hid>
Cc: xenomai@xenomai.org
Subject: RE: [Xenomai-help] my tick takes a break !!
Date: Wed, 19 Apr 2006 22:34:04 +0200 [thread overview]
Message-ID: <17478.40636.563067.656256@domain.hid> (raw)
In-Reply-To: <5B122FD931231D408AC32630D1B1F7290AC5B129@domain.hid>
Thomas, Brieuc \(GE Healthcare\) wrote:
>
> Thomas, Brieuc \(GE Healthcare\) wrote:
> > Hi every one !
> >
> > I really don't understand, my porting of application works very well
> > (under vxworks skin), message, semaphore, timer... Except the task !!
> > I've got a curious behaviour, when I've got a heavy task, the kernel
> > tick counter stop during the process!!
> >
> > And take back when this one is finish.
> >
> > Therefore the other tasks are freeze and my application crash.
> >
> >
> >
> > have You already seen this case?
>
> I do not know if it is what you mean, but when running Xenomai, your
> tasks are supposed to suspend sufficiently frequently to leave Linux
> tick normally. This means that if you configured CONFIG_HZ=100, your
> real-time activity (including kernel-space tasks and user-space tasks in
> primary mode) is supposed to take a break at least once every 1/100
> second.
>
> --
>
>
> Gilles Chanteperdrix.
>
> Oh no! Sorry, I mean the real-time tick counter!
If the heavy task is using intLock() then yes, it will prevent the timer
from ticking. If you are observing something else, could you send to
this mailing list a minimal test case illustrating what you are
observing?
> But if my real-time activity don't take a break during a while (more
> than 1/100 second), Is it dangerous for my real-time activity?
If you do not let Linux run often enough, it will crash, and this is
dangerous for your real-time activity.
I do not know exactly how much is "often enough", and it probably
depends on many factors, but if you want Linux timed services to work
normally, you should let Linux timer tick regularly.
--
Gilles Chanteperdrix.
next prev parent reply other threads:[~2006-04-19 20:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-19 16:55 [Xenomai-help] my tick takes a break !! Thomas, Brieuc (GE Healthcare)
2006-04-19 20:34 ` Gilles Chanteperdrix [this message]
2006-04-21 13:56 ` Gilles Chanteperdrix
-- strict thread matches above, loose matches on Subject: below --
2006-04-24 9:49 Thomas, Brieuc (GE Healthcare)
2006-04-24 13:27 ` Gilles Chanteperdrix
2006-04-24 13:37 ` Philippe Gerum
2006-04-24 13:44 ` Gilles Chanteperdrix
2006-04-24 14:06 ` Philippe Gerum
2006-04-24 14:16 ` Gilles Chanteperdrix
2006-04-24 14:32 ` Philippe Gerum
2006-04-21 16:16 Thomas, Brieuc (GE Healthcare)
2006-04-23 12:53 ` Gilles Chanteperdrix
2006-04-20 9:23 Thomas, Brieuc (GE Healthcare)
2006-04-19 15:05 Thomas, Brieuc (GE Healthcare)
2006-04-19 15:18 ` Gilles Chanteperdrix
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=17478.40636.563067.656256@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=Brieuc.Thomas@domain.hid \
--cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.