From: Nick Garnett <nickg@cygnus.co.uk>
To: "Alan Cudmore" <Alan.P.Cudmore.1@gsfc.nasa.gov>
Cc: "elix mailing list" <elix@sourceware.cygnus.com>
Subject: Re: Posix message queues in linux?
Date: Thu, 24 Feb 2000 06:30:00 -0000 [thread overview]
Message-ID: <por9e27jwy.fsf@balti.cygnus.co.uk> (raw)
In-Reply-To: <001501bf7d73$25e726c0$c3ddb780@rtos.gsfc.nasa.gov>
"Alan Cudmore" <Alan.P.Cudmore.1@gsfc.nasa.gov> writes:
> Hi,
> I sent this message to the mailing list before, but I figured that everyone
> was at Linuxworld in New York :)
>
> I was reading the EL/IX draft spec under 3.13 Message Passing:
>
> Does linux support POSIX message passing?
> If linux does not support it, is it going to be part of an EL/IX API that
> runs on Linux?
At present Linux does not support message passing. This is a minor
problem with some parts of the EL/IX specification: Linux is not yet
fully POSIX compliant. We expect this to change - there are already
patches available for some areas, and others are amenable to a
user-level implementation in glibc.
>
> Is there a better way to do message passing in Linux & EL/IX. I am looking
> to have a capability similar to the RTOSs I am used to such as vxWorks and
> Nucleus.
>
I do not believe that Linux provides any alternative message passing
mechanism - unless you count pipes! Since one of the goals of EL/IX is
to work with existing standards as much as possible, it would not be
appropriate for us to define a whole new message passing mechanism. I
do agree, however, that the message passing facilities in POSIX fall
somewhat short of what other RTOSs provide.
--
Nick Garnett
Cygnus Solutions, a Red Hat Company
Cambridge, UK
prev parent reply other threads:[~2000-02-24 6:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-22 12:23 Alan Cudmore
2000-02-24 6:02 ` Stuart Hughes
2000-02-24 6:30 ` Nick Garnett [this message]
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=por9e27jwy.fsf@balti.cygnus.co.uk \
--to=nickg@cygnus.co.uk \
--cc=Alan.P.Cudmore.1@gsfc.nasa.gov \
--cc=elix@sourceware.cygnus.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).