From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Markus.Franke@domain.hid
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] rt_pipe_write() returns -ENOMEM
Date: Mon, 05 Mar 2007 17:17:18 +0100 [thread overview]
Message-ID: <45EC428E.5060306@domain.hid> (raw)
In-Reply-To: <45EC4111.6070104@domain.hid>
Markus Franke wrote:
> Dear Xenomai Developers/Users,
>
> I want to exchange data between User Space and Kernel Space via a
> Message Pipe. Therefore I set up a pipe via rt_pipe_create() and write
> to the pipe using rt_pipe_write(). After a few writes rt_pipe_write()
> returns -ENOMEM what means that memory is exhausted. What happens if I
> just ignore this error code? Does it simply mean that values are dropped
> until the first value is read from the pipe by the User-Space Task? If
> so, how can I increase the size of the message pipe? rt_pipe_alloc()
> doesn't seem to solve the problem, isn't it?
The fourth argument of rt_pipe_create is the size of the reserved pool
used by the pipe. If you pass 0, the system heap is used. The size of
the system heap is configured via the kernel configuration.
rt_pipe_alloc allocates a message from the used pool (the rt_pipe pool
if you passed a non 0 pool size to rt_pipe_create, or the system heap if
you passed a null pool size to rt_pipe_create).
--
Gilles Chanteperdrix
next prev parent reply other threads:[~2007-03-05 16:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-05 16:10 [Xenomai-help] rt_pipe_write() returns -ENOMEM Markus Franke
2007-03-05 16:17 ` Gilles Chanteperdrix [this message]
2007-03-05 16:53 ` Markus Franke
2007-03-05 17:12 ` Gilles Chanteperdrix
2007-03-05 17:54 ` Markus Franke
2007-03-05 18:30 ` Gilles Chanteperdrix
2007-03-05 20:12 ` Gilles Chanteperdrix
2007-03-05 23:51 ` Markus Franke
2007-03-08 15:55 ` 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=45EC428E.5060306@domain.hid \
--to=gilles.chanteperdrix@xenomai.org \
--cc=Markus.Franke@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.