From owner-freebsd-threads@FreeBSD.ORG  Wed Apr 16 09:36:01 2003
Return-Path: <owner-freebsd-threads@FreeBSD.ORG>
Delivered-To: freebsd-threads@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 5256137B401; Wed, 16 Apr 2003 09:36:01 -0700 (PDT)
Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 7439F43FD7; Wed, 16 Apr 2003 09:36:00 -0700 (PDT)
	(envelope-from eischen@pcnet1.pcnet.com)
Received: from pcnet1.pcnet.com (localhost [127.0.0.1])
	by mail.pcnet.com (8.12.8/8.12.1) with ESMTP id h3GGZvBg016860;
	Wed, 16 Apr 2003 12:35:57 -0400 (EDT)
Received: from localhost (eischen@localhost)h3GGZv01016856;
	Wed, 16 Apr 2003 12:35:57 -0400 (EDT)
Date: Wed, 16 Apr 2003 12:35:57 -0400 (EDT)
From: Daniel Eischen <eischen@pcnet1.pcnet.com>
To: John Polstra <jdp@polstra.com>
In-Reply-To: <XFMail.20030416092903.jdp@polstra.com>
Message-ID: <Pine.GSO.4.10.10304161232120.14483-100000@pcnet1.pcnet.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: deischen@freebsd.org
cc: jeff@freebsd.org
cc: freebsd-threads@freebsd.org
Subject: Re: May I add pthread_[gs]etconcurrency to the threads libraries?
X-BeenThere: freebsd-threads@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Threading on FreeBSD <freebsd-threads.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
	<mailto:freebsd-threads-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-threads>
List-Post: <mailto:freebsd-threads@freebsd.org>
List-Help: <mailto:freebsd-threads-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
	<mailto:freebsd-threads-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2003 16:36:01 -0000

On Wed, 16 Apr 2003, John Polstra wrote:

> Hi Guys,
> 
> Sergey Osokin sent me patches to add the standard
> pthread_[gs]etconcurrency functions to our various threads
> libraries.  I reviewed them and they're OK.  The functions don't do
> anything significant, but they fill the need for this part of the
> API.
> 
> OK if I commit them this weekend?  The changes don't change anything
> else.  They just add stuff.

I'm about to implement them for real in libpthread.  I'd appreciate
you not adding them to that.  I've got a slew of other changes that
I want add to it very soon.

They don't seem to make sense for libthr and libc_r unless it
returns ENOTSUP.  libthr is 1:1, so it is meaning less there
as well as libc_r.

-- 
Dan Eischen