From: Jan Kiszka <jan.kiszka@domain.hid>
To: NZG <ngustavson@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] Fwd: can't use message pipe - Cannot allocate memory
Date: Thu, 07 Jun 2007 21:27:29 +0200 [thread overview]
Message-ID: <46685C21.5020709@domain.hid> (raw)
In-Reply-To: <200706071337.07691.ngustavson@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 894 bytes --]
NZG wrote:
>>> Write does stop throwing errors with a pool of 16384.
>> Just repeating for confirmation: rt_pipe_create with smaller, but
>> non-zero pool sizes doesn't report some error?
> Incorrect, if it's created with smaller it does report an error. If it's
> created with 0 however, it seems ok. (at least it doesn't throw an error)
You mean the write fails, but rt_pipe_create is fine. At least here, and
Philippe noticed the same. Looks like the margin for minimal-sized heaps
is broken. 2*PAGE_SIZE should be 3*PAGE_SIZE net space, Philippe?
>
>> Pipes are asymmetric: RT<->NRT only.
> RT<->NRT is my goal.
> essentially I
> 1. spawn off a real time task which creates a pipe to receive commands
> 2. throw commands at it from the user space thread which spawned the real time
> process (which is still NRT correct? I'm fuzzy on this).
It is NRT.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
next prev parent reply other threads:[~2007-06-07 19:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-07 15:49 [Xenomai-help] Fwd: can't use message pipe - Cannot allocate memory NZG
2007-06-07 17:03 ` Philippe Gerum
2007-06-07 17:19 ` Philippe Gerum
2007-06-07 18:11 ` NZG
2007-06-07 18:22 ` Jan Kiszka
2007-06-07 18:37 ` NZG
2007-06-07 19:27 ` Jan Kiszka [this message]
2007-06-07 19:39 ` NZG
2007-06-07 20:15 ` Philippe Gerum
2007-06-07 22:29 ` Philippe Gerum
2007-06-07 22:47 ` Jan Kiszka
2007-06-08 6:55 ` [Xenomai-core] " Philippe Gerum
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=46685C21.5020709@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=ngustavson@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.