All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jack Whorn" <jackwhorn@domain.hid>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Preemptive scheduling
Date: Tue, 03 Apr 2007 22:05:39 +0200	[thread overview]
Message-ID: <20070403200539.126240@domain.hid> (raw)
In-Reply-To: <460B7CE0.60107@domain.hid>

Hi Gilles, Hi folks,

The data is stored by a thread that periodically issues a single call to
rt_task_set_mode(0, T_PRIMARY, NULL) followed by several file operation calls like fprintf() and finally a call to fflush(NULL) and sync().

The application is not a kernel module, so - as far as I see it - it is a user mode thread, and it actually has the highest priority in my system.

Does this help understanding the phenomenon?

Regards,

Jack

> Jack Whorn wrote:
> > Hi Gilles,
> > 
> > 
> >>Once your program enters this infinte loop, it never gets out, so :
> >>- your assumption that "t_task_set_mode periodically clears T_LOCK and
> >>  T_SHIELD and sets T_RRB" is false;
> > 
> > 
> > Yeah, I just realized that it does this only once. According to
> http://snail.fsffrance.org/www.xenomai.org/documentation/branches/v2.0.x/html/api/group__task.html#ga44But
> I think that the arguments used in the rt_task_set_mode() -call are
> correct. Isn't that sufficient for the Linux OS to catch e.g. keyboard
> interrupts?
> > 
> > 
> >>- even if higher priority task runs, Linux, which is Xenomai idle task
> >>  never runs, so the system locks up.
> > 
> > 
> > Gotcha, that sounds sensible to me.
> > 
> > Actually, the higher-priority task uses some linux-system calls to store
> data to hard disk. This does no longer take place as soon as the infinite
> loop is entered. I expected priority coupling to solve that. Where is my
> error in reasoning?
> 
> Maybe storing data to the disk requires a kernel thread to flush them.
> If this thread never has a chance to run, then your data are written in
> the cache but never flushed to the disk. I may be wrong, but I am almost
> sure that if you let Linux run, everything will go as expected.
> 
> If I am wrong, please, send us a self-contained example program which
> demonstrates the behaviour you observed.
> 
> -- 
>                                                  Gilles Chanteperdrix

-- 
"Feel free" - 10 GB Mailbox, 100 FreeSMS/Monat ...
Jetzt GMX TopMail testen: http://www.gmx.net/de/go/topmail


  reply	other threads:[~2007-04-03 20:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-28 20:31 [Xenomai-help] Preemptive scheduling Jack Whorn
2007-03-28 21:20 ` Gilles Chanteperdrix
2007-03-29  3:17   ` Jack Whorn
2007-03-29  8:46     ` Gilles Chanteperdrix
2007-04-03 20:05       ` Jack Whorn [this message]
2007-04-03 20:24         ` Philippe Gerum
2007-04-03 20:55           ` Jack Whorn
2007-04-04  8:17             ` Philippe Gerum
2007-04-04 15:10               ` Jack Whorn
2007-04-05 18:38                 ` Philippe Gerum
2007-04-10 22:47                   ` Jack Whorn
2007-04-11  8:15                     ` Dmitry Adamushko

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=20070403200539.126240@domain.hid \
    --to=jackwhorn@domain.hid \
    --cc=gilles.chanteperdrix@xenomai.org \
    --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.