From owner-freebsd-threads@FreeBSD.ORG  Wed Apr 16 09:43:00 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 CC62437B401; Wed, 16 Apr 2003 09:43:00 -0700 (PDT)
Received: from mail.chesapeake.net (chesapeake.net [205.130.220.14])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id B011543FCB; Wed, 16 Apr 2003 09:42:59 -0700 (PDT)
	(envelope-from jroberson@chesapeake.net)
Received: from localhost (jroberson@localhost)
	by mail.chesapeake.net (8.11.6/8.11.6) with ESMTP id h3GGgeC76025;
	Wed, 16 Apr 2003 12:42:40 -0400 (EDT)
	(envelope-from jroberson@chesapeake.net)
Date: Wed, 16 Apr 2003 12:42:40 -0400 (EDT)
From: Jeff Roberson <jroberson@chesapeake.net>
To: Daniel Eischen <eischen@pcnet1.pcnet.com>
In-Reply-To: <Pine.GSO.4.10.10304161232120.14483-100000@pcnet1.pcnet.com>
Message-ID: <20030416123956.Q76635-100000@mail.chesapeake.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: deischen@freebsd.org
cc: jeff@freebsd.org
cc: freebsd-threads@freebsd.org
cc: John Polstra <jdp@polstra.com>
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:43:01 -0000


On Wed, 16 Apr 2003, Daniel Eischen wrote:

> 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.

It is not meaningless.  Please go ahead and implement stubs if you like.
I intended to implement a thr_setconcurrency that these can eventually
use.  I was just going to implement it as a simple counter on the proc
instead of using a full blown KSE structure just for this.

1:1 means one kernel thread for each user thread.  It doesn't say anything
about how many of those threads may run at a given time.  It also doesn't
force any scheduling scope or scheduling algorithm.

Cheers,
Jeff