From: Michel Rinaldi <automation.03@domain.hid>
To: xenomai@xenomai.org
Subject: [Xenomai-help] Problems with rt_task_create and rt_task_join
Date: Fri, 21 Jan 2011 18:01:26 +0100 (CET) [thread overview]
Message-ID: <22767829.221295629285203.JavaMail.SYSTEM@PC-MRINALDI> (raw)
In-Reply-To: <14515395.201295629170328.JavaMail.SYSTEM@PC-MRINALDI>
[-- Attachment #1: Type: text/plain, Size: 1209 bytes --]
Hi to all,
I'm running an application on a Linux system with kernel 2.6.35.7 patched with Xenomai 2.5.5.2, Adeos ipipe patch 2.7-04.
My application uses native skin and creates some realtime tasks, each with rt_task_shadow(), each other with rt_task_create(). When I call for first time rt_task_create(), this function is very slow (700-800 ms) to execute, also if rt_task_shadow() calls come first. Subsequent calls of rt_task_create() are quick as expected. I read on manual that at first call rt_task_create() creates a signal handler for SIGWINCH signal: could be this operation that wastes time, maybe on waiting some resources from Linx kernel?
Another problem that I've encountered is that if I call a rt_int_delete() and then a rt_task_join() on userspace task that handles destroyed IRQ, rt_task_join() never returns (obviously this task was created with joinable flag). If I create this task without joinable flag and then I call rt_task_delete() instead rt_task_join() I obtain two different behaviours: sometimes rt_task_delete() returns but I still view task on /proc/xenomai/sched (with X status), sometimes system freezes on this call.
Thanks to all in advance.
Regards
Mauro Salvini
[-- Attachment #2: Type: text/html, Size: 1406 bytes --]
next parent reply other threads:[~2011-01-21 17:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <14515395.201295629170328.JavaMail.SYSTEM@PC-MRINALDI>
2011-01-21 17:01 ` Michel Rinaldi [this message]
2011-01-21 17:11 ` [Xenomai-help] Problems with rt_task_create and rt_task_join Philippe Gerum
2011-01-22 14:26 ` Mauro
2011-01-22 19:14 ` Gilles Chanteperdrix
2011-01-24 14:05 ` Michel Rinaldi
2011-01-24 14:27 ` Gilles Chanteperdrix
[not found] <24653571.21295878006500.JavaMail.SYSTEM@PC-MRINALDI>
2011-01-24 14:07 ` Michel Rinaldi
[not found] <22536578.91295887083468.JavaMail.SYSTEM@PC-MRINALDI>
2011-01-24 16:39 ` Michel Rinaldi
2011-01-24 16:44 ` Gilles Chanteperdrix
2011-01-24 16:54 ` Gilles Chanteperdrix
[not found] <20964580.81295961364859.JavaMail.SYSTEM@PC-MRINALDI>
2011-01-25 13:17 ` Michel Rinaldi
2011-01-25 13:26 ` Gilles Chanteperdrix
[not found] <11269195.111296118370328.JavaMail.SYSTEM@PC-MRINALDI>
2011-01-27 8:58 ` Michel Rinaldi
2011-01-27 13:36 ` Gilles Chanteperdrix
[not found] <29582899.21296203622078.JavaMail.SYSTEM@PC-MRINALDI>
2011-01-28 8:34 ` Michel Rinaldi
2011-01-28 17:43 ` Gilles Chanteperdrix
[not found] <21381658.41297350790328.JavaMail.SYSTEM@pc-msalvini>
2011-02-10 15:20 ` Mauro Salvini
2011-02-10 16:14 ` Gilles Chanteperdrix
[not found] <8701358.01297411757328.JavaMail.SYSTEM@pc-msalvini>
2011-02-11 8:10 ` Mauro Salvini
2011-02-11 9:56 ` 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=22767829.221295629285203.JavaMail.SYSTEM@PC-MRINALDI \
--to=automation.03@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.