From: Manfred Spraul <manfred@colorfullife.com>
To: Peter Waechtler <pwaechtler@mac.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] unified SysV and Posix mqueues as FS
Date: Mon, 28 Oct 2002 22:43:26 +0100 [thread overview]
Message-ID: <3DBDAF7E.3040309@colorfullife.com> (raw)
In-Reply-To: 3DBDAE85.B4499B8F@mac.com
Peter Waechtler wrote:
>>For the locking stuff, the patch should probably depend on the sysv rcu
>>patch, it cleans up locking a bit.
>>
>>
>>
>
>Well, I am a victim of "information hiding" ;-)
>
>
That's not information hiding - there were 3 different locking
implementations: first one with a per-queue spinlock that didn't support
growing the number of queues at runtime, then one with a global rw lock
and a per-queue spinlock, and the simple, global spinlock version that's
part of 2.3.x-2.5.4x.
>msq_lock(id) does not lock a queue, it locks/unlocks the whole array.
>Forget my post about a deadlock in ipc_addid()
>
>
Which deadlock did you see? With the RCU ipc patch [part of 2.5.44-mm6],
msg_lock again locks the queue, not the whole array. Calls to
ipc_addid() with the msq spinlock aquired are not permitted.
--
Manfred
next prev parent reply other threads:[~2002-10-28 21:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-27 16:55 [PATCH] unified SysV and Posix mqueues as FS Manfred Spraul
2002-10-27 22:05 ` Peter Waechtler
[not found] ` <3DBCDF4A.3080709@colorfullife.com>
2002-10-28 10:49 ` Peter Waechtler
2002-10-28 21:39 ` Peter Waechtler
2002-10-28 21:43 ` Manfred Spraul [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-27 15:33 Peter Waechtler
2002-10-27 15:47 ` Jeff Garzik
2002-10-27 15:53 ` Alexander Viro
2002-10-27 19:49 ` H. Peter Anvin
2002-10-27 22:02 ` Peter Waechtler
2002-10-28 1:54 ` Alexander Viro
2002-10-28 10:44 ` Peter Waechtler
2002-10-28 22:18 ` Bill Davidsen
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=3DBDAF7E.3040309@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pwaechtler@mac.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 NNTP newsgroup(s).