From: Nick Garnett <nickg@cygnus.co.uk>
To: elix@sourceware.cygnus.com
Subject: Re: EL/IX spec review, status
Date: Wed, 19 Jan 2000 02:57:00 -0000 [thread overview]
Message-ID: <po4scauy5k.fsf@balti.cygnus.co.uk> (raw)
In-Reply-To: <200001182238.OAA09832@triplerock.olsons.net>
"Michael A. Olson" <mao@sleepycat.com> writes:
> My argument is that shared memory is a useful abstraction for
> multi-process, and belongs there.
>
Thanks for your comments.
You are right about this, we started off trying to be as ruthless as
possible in taking things out of the APIs. The shared memory
interfaces were one of those things that I was not sure
about so I followed the old adage - "When in doubt, leave it out".
The POSIX 1003.13 Real Time Profiles document adds shared memory
objects and memory mapped files to its Realtime Controller
profile. This is roughly equivalent to our level 2. I still need time
to evaluate these profiles against EL/IX, but we might end up with the
shared memory stuff at level 2.
I have provisionally moved all the shared memory stuff into level 3 in
my current working version of the spec.
--
Nick Garnett
Red Hat, Cambridge, UK
prev parent reply other threads:[~2000-01-19 2:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-18 11:15 Michael A. Olson
2000-01-18 12:24 ` Peter Buechler
2000-01-18 14:25 ` Bas Valkema
2000-01-18 14:38 ` Michael A. Olson
2000-01-19 2:57 ` 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=po4scauy5k.fsf@balti.cygnus.co.uk \
--to=nickg@cygnus.co.uk \
--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).