From: Ulrich Drepper <drepper@redhat.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: torvalds@transmeta.com (Linus Torvalds),
viro@math.psu.edu (Alexander Viro),
abramo@alsa-project.org (Abramo Bagnara),
alonz@nolaviz.org (Alon Ziv),
linux-kernel@vger.kernel.org (Kernel Mailing List),
mkravetz@sequent.com (Mike Kravetz)
Subject: Re: light weight user level semaphores
Date: 19 Apr 2001 13:06:45 -0700 [thread overview]
Message-ID: <m3lmow1woa.fsf@otr.mynet.cygnus.com> (raw)
In-Reply-To: <E14qKDi-0007sy-00@the-village.bc.nu>
In-Reply-To: Alan Cox's message of "Thu, 19 Apr 2001 20:35:59 +0100 (BST)"
Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
> mknod foo p. Or use sockets (although AF_UNIX sockets are higher latency)
> Thats why I suggested using flock - its name based. Whether you mkstemp()
> stuff and pass it around isnt something I care about
>
> Files give you permissions for free too
I don't want nor need file permissions. A program would look like this:
process 1:
fd = open("somefile")
addr = mmap(fd);
pthread_mutexattr_init(&attr);
pthread_mutexattr_setpshared(&attr, PTHREAD_PROCESS_SHARED);
pthread_mutex_init ((pthread_mutex_t *) addr, &attr);
pthread_mutex_lock ((pthread_mutex_t *) addr);
pthread_mutex_destroy((pthread_mutex_t *) addr);
process 2:
fd = open("somefile")
addr = mmap(fd);
pthread_mutex_lock ((pthread_mutex_t *) addr);
The shared mem segment can be retrieved in whatever way. The mutex in
this case is anonymous. Everybody who has access to the shared mem
*must* have access to the mutex.
For semaphores it looks similarly. First the anonymous case:
process 1:
fd = open("somefile")
addr = mmap(fd);
sem_init ((sem_t *) addr, 1, 10); // 10 is arbitrary
sem_wait ((sem_t *) addr);
sem_destroy((sem_t *) addr);
process 2:
fd = open("somefile")
addr = mmap(fd);
sem_wait ((sem_t *) addr);
Note that POSIX semaphores could be implemented with global POSIX
mutexes.
Finally, named semaphores:
semp = sem_open("somefile", O_CREAT|O_EXCL, 0600)
sem_wait (semp);
sem_close(semp);
sem_unlink(semp);
This is the only semaphore kind which maps nicely to a pipe or socket.
All the others don't. And even for named semaphores it is best to
have a separate name space like the shmfs.
> So you have unix file permissions on them ?
See above. Permissions are only allowed for named semaphores.
--
---------------. ,-. 1325 Chesapeake Terrace
Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
Red Hat `--' drepper at redhat.com `------------------------
next prev parent reply other threads:[~2001-04-19 20:08 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20010417114433.D1108@w-mikek2.sequent.com>
2001-04-17 19:48 ` Linus Torvalds
2001-04-18 18:13 ` Bernd Eckenfels
2001-04-18 19:35 ` Ulrich Drepper
2001-04-19 8:20 ` Alon Ziv
2001-04-19 8:52 ` Abramo Bagnara
2001-04-19 9:08 ` Alexander Viro
2001-04-19 10:44 ` Abramo Bagnara
2001-04-19 16:11 ` Linus Torvalds
2001-04-19 16:33 ` Alexander Viro
2001-04-19 16:43 ` Linus Torvalds
2001-04-19 17:33 ` Alexander Viro
2001-04-19 17:38 ` Linus Torvalds
2001-04-19 18:24 ` Alexander Viro
2001-04-19 19:26 ` Ulrich Drepper
2001-04-19 19:35 ` Alan Cox
2001-04-19 20:06 ` Ulrich Drepper [this message]
2001-04-19 20:11 ` Alan Cox
2001-04-19 20:26 ` Ulrich Drepper
2001-04-19 20:22 ` Ingo Oeser
2001-04-19 20:40 ` Ulrich Drepper
2001-04-19 20:51 ` Linus Torvalds
2001-04-19 21:38 ` Alan Cox
2001-04-19 20:49 ` Linus Torvalds
2001-04-19 21:18 ` Ulrich Drepper
2001-04-19 21:41 ` Linus Torvalds
2001-04-19 22:46 ` Ulrich Drepper
2001-04-20 1:35 ` Alexander Viro
2001-04-20 2:45 ` Ulrich Drepper
2001-04-19 16:43 ` Abramo Bagnara
2001-04-19 20:47 ` Ingo Oeser
2001-04-19 20:54 ` Linus Torvalds
2001-04-19 9:08 ` Ingo Oeser
2001-04-19 11:51 ` Alan Cox
2001-04-19 16:03 ` Linus Torvalds
2001-04-19 16:38 ` Alan Cox
2001-04-19 16:46 ` Linus Torvalds
2001-04-19 17:12 ` Alan Cox
2001-04-19 22:35 ` Rogier Wolff
2001-04-20 9:29 ` Olaf Titz
2001-04-20 14:19 ` Jesse Pollard
2001-04-20 18:36 ` Olaf Titz
2001-04-20 23:33 ` Linus Torvalds
2001-04-21 4:06 ` fd allocation [was: light weight user level semaphores] Edgar Toernig
2001-04-22 9:48 ` Olaf Titz
2001-04-22 11:41 ` light weight user level semaphores Alon Ziv
2001-04-22 12:44 ` Alan Cox
2001-04-22 15:19 ` Alon Ziv
2001-04-22 14:31 ` Alexander Viro
2001-04-22 16:08 ` Alon Ziv
2001-04-22 11:41 ` Alon Ziv
2001-04-22 14:18 ` David Woodhouse
2001-04-23 13:19 ` David Howells
2001-04-23 14:48 ` Alon Ziv
2001-04-23 15:40 ` David Howells
2001-04-21 10:13 ` Olaf Titz
2001-04-23 15:34 ` Jeff Garzik
2001-04-23 19:18 ` Ingo Oeser
2001-04-24 0:19 ` David Wagner
2001-04-24 0:41 ` Alexander Viro
2001-04-19 19:47 ` Ulrich Drepper
2001-04-19 18:48 ` Olaf Titz
2001-04-19 13:59 George Talbot
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=m3lmow1woa.fsf@otr.mynet.cygnus.com \
--to=drepper@redhat.com \
--cc=abramo@alsa-project.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=alonz@nolaviz.org \
--cc=drepper@cygnus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mkravetz@sequent.com \
--cc=torvalds@transmeta.com \
--cc=viro@math.psu.edu \
/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
all inboxes | Powered by JetHome®