From: Manfred Spraul <manfred@colorfullife.com>
To: mingo@elte.hu
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] POSIX message queues
Date: Wed, 04 Sep 2002 18:03:21 +0200 [thread overview]
Message-ID: <3D762EC9.1040105@colorfullife.com> (raw)
Ingo wrote:
> On Sun, 1 Sep 2002, Amos Waterland wrote:
>
>> That is the fundamental problem with a userspace shared memory
>> implementation: write permissions on a message queue should grant
>> mq_send(), but write permissions on shared memory grant a lot more than
>> just that.
>
> is it really a problem? As long as the read and write queues are separated
> per sender, all that can happen is that a sender is allowed to read his
> own messages - that is not an exciting capability.
>
Messages with the same prio are ordered - a separated per sender queue
would break SuS.
--
Manfred
next reply other threads:[~2002-09-04 15:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-04 16:03 Manfred Spraul [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-29 21:53 [PATCH] POSIX message queues pwaechtler
2002-08-30 9:48 ` Amos Waterland
2002-08-31 11:43 ` pwaechtler
2002-08-31 13:14 ` Krzysztof Benedyczak
2002-09-01 0:22 ` Amos Waterland
2002-09-01 1:50 ` Amos Waterland
2002-09-04 11:13 ` Ingo Molnar
2002-09-06 10:04 ` Pavel Machek
2002-09-07 14:16 ` pwaechtler
2002-09-06 22:48 ` Amos Waterland
2002-09-07 14:11 ` pwaechtler
2002-09-07 15:17 ` Ingo Molnar
2002-09-08 22:00 ` Amos Waterland
2002-08-31 12:53 ` Krzysztof Benedyczak
2002-09-07 14:39 ` pwaechtler
2002-08-27 21:48 Krzysztof Benedyczak
2002-08-27 22:16 ` Christoph Hellwig
2002-08-31 13:28 ` Krzysztof Benedyczak
2002-09-01 7:24 ` Jakub Jelinek
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=3D762EC9.1040105@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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.