From owner-freebsd-arch@FreeBSD.ORG  Tue Dec 14 03:35:37 2004
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id B6C9216A4CE; Tue, 14 Dec 2004 03:35:37 +0000 (GMT)
Received: from mail.ntplx.net (mail.ntplx.net [204.213.176.10])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 5FAB843D1D; Tue, 14 Dec 2004 03:35:37 +0000 (GMT)
	(envelope-from deischen@freebsd.org)
Received: from sea.ntplx.net (sea.ntplx.net [204.213.176.11])
	iBE3ZWHr027103;	Mon, 13 Dec 2004 22:35:32 -0500 (EST)
Date: Mon, 13 Dec 2004 22:35:32 -0500 (EST)
From: Daniel Eischen <deischen@freebsd.org>
X-X-Sender: eischen@sea.ntplx.net
To: Joe Kelsey <joe@zircon.seattle.wa.us>
In-Reply-To: <1102994420.30309.219.camel@zircon.zircon.seattle.wa.us>
Message-ID: <Pine.GSO.4.43.0412132230310.7677-100000@sea.ntplx.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Virus-Scanned: by AMaViS and Clam AntiVirus (mail.ntplx.net)
cc: arch@freebsd.org
cc: David Schultz <das@freebsd.org>
cc: Julian Elischer <julian@elischer.org>
Subject: Re: Fixing Posix semaphores
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: Daniel Eischen <deischen@freebsd.org>
List-Id: Discussion related to FreeBSD architecture
	<freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Dec 2004 03:35:37 -0000

On Mon, 13 Dec 2004, Joe Kelsey wrote:

> On Mon, 2004-12-13 at 18:34 -0500, David Schultz wrote:
> >
> > Err, I'm pretty sure Solaris uses a separate namespace for
> > semaphores, and I think Linux does the same.  That's not to say
> > that I'm opposed to this idea.  However, the implementation you
> > propose, while aesthetically pleasing, is likely to be much slower
> > and take a good deal of effort.  Moreover, it doesn't seem that it
> > would provide any significant additional functionality.
>
> The Solaris documentation specifically says that sem_open uses file
> system namespace.

It doesn't in the man page for sem_open().  From a Solaris 9
box:

$ man sem_open

	[ ... ]

     The name argument points to  a  string  naming  a  semaphore
     object.  It  is  unspecified whether the name appears in the
     file system and is visible to functions that take  pathnames
     as arguments. The name argument conforms to the construction
     rules for a pathname. The first character of  name must be a
     slash   (/)  character and the remaining characters of  name
     cannot include any slash characters.  For maximum  portabil-
     ity,   name  should  include no more than 14 characters, but
     this limit is not enforced.

	[ ... ]

-- 
DE