From: Jan Kiszka <jan.kiszka@domain.hid>
To: Dmitry Adamushko <dmitry.adamushko@domain.hid>
Cc: Xenomai help <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] [RT_PIPE] - User space read() not waking up
Date: Fri, 23 Mar 2007 09:49:44 +0100 [thread overview]
Message-ID: <460394A8.5010501@domain.hid> (raw)
In-Reply-To: <b647ffbd0703230142n46a215ddv5ab0e2c984d0d93c@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 687 bytes --]
Dmitry Adamushko wrote:
> [...]
>> So basically, my question is:
>> If I have rt_pipe_write() writing to a pipe from a kernel module with a
>> 200 us period and I have a read() in a tight loop reading from that same
>> pipe is user space, what could be the origin of the fact that
>> sometimes my
>> read() doesn't get woken up?
>
>
> Xenomai does provide a Linux system with hard real-time support but it
> doesn't make the Linux kernel itself hard real-time, nor user-space
> applications which relies merely on the standard kernel services.
Good that you read the mail more thoroughly than I did... :-/
Yes, that's obviously an application design issue.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
next prev parent reply other threads:[~2007-03-23 8:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 21:57 [Xenomai-help] [RT_PIPE] - User space read() not waking up Viktor Stark
2007-03-23 8:38 ` Jan Kiszka
2007-03-23 8:42 ` Dmitry Adamushko
2007-03-23 8:49 ` Jan Kiszka [this message]
2007-03-24 1:48 ` Viktor STARK
[not found] ` <460481F2.5010408@domain.hid>
2007-03-24 10:20 ` Dmitry Adamushko
2007-03-24 11:55 ` Philippe Gerum
2007-03-24 12:07 ` Viktor STARK
2007-03-24 22:49 ` Philippe Gerum
2007-03-25 0:23 ` Viktor STARK
2007-03-24 22:36 ` [off-list] " 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=460394A8.5010501@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=dmitry.adamushko@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.