From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Jan Kiszka <jan.kiszka@domain.hid>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] interrupt service routine issue
Date: Thu, 29 Jan 2009 16:00:47 +0000 [thread overview]
Message-ID: <4981D2AF.3040607@domain.hid> (raw)
In-Reply-To: <4981D1AA.7050308@domain.hid>
Jan Kiszka wrote:
> Gilles Chanteperdrix wrote:
>> stefano.franzoni@domain.hid wrote:
>>> Thanks Gilles,
>>>
>>> with your suggestion, setting the special mode bit T_WARNSW for the
>>> incriminated task, we found two critical functions that caused switches to
>>> secondary mode.
>>>
>>> I report them for documentation:
>>>
>>> 1. We used mmap function used to map a file into memory. The access to the
>>> memory caused sometimes the switch to secondary mode.
>> damn, this should not happen, we use mlockall and some additional tricks
>> in the I-pipe patch to avoid that.
>
> Mmmh, I don't think we can cure (/wrt RT) access to memory mapped files.
> That's just the same no-go for RT threads as other Linux I/O.
Well, normally, with mlockall, if you call mmap, the whole file is
loaded in memory. Of course, if there are "holes" in your file, a write
to the file will cause a fault.
--
Gilles.
next prev parent reply other threads:[~2009-01-29 16:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-28 13:20 [Xenomai-help] interrupt service routine issue stefano.franzoni
2009-01-28 13:38 ` Gilles Chanteperdrix
2009-01-29 15:22 ` stefano.franzoni
2009-01-29 15:39 ` Gilles Chanteperdrix
2009-01-29 15:56 ` Jan Kiszka
2009-01-29 16:00 ` Gilles Chanteperdrix [this message]
2009-01-29 16:51 ` stefano.franzoni
2009-01-29 16:54 ` Gilles Chanteperdrix
2009-01-28 13:46 ` 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=4981D2AF.3040607@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=jan.kiszka@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.