From owner-freebsd-threads@FreeBSD.ORG Wed Apr 16 09:42:14 2003 Return-Path: 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 6450337B401; Wed, 16 Apr 2003 09:42:14 -0700 (PDT) Received: from wall.polstra.com (wall-gw.polstra.com [206.213.73.130]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4AFCE43F85; Wed, 16 Apr 2003 09:42:11 -0700 (PDT) (envelope-from jdp@polstra.com) Received: from strings.polstra.com (strings.polstra.com [206.213.73.20]) by wall.polstra.com (8.12.3p2/8.12.3) with ESMTP id h3GGgAds022903; Wed, 16 Apr 2003 09:42:10 -0700 (PDT) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.5.1 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 16 Apr 2003 09:42:10 -0700 (PDT) Organization: Polstra & Co., Inc. From: John Polstra To: Daniel Eischen 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Apr 2003 16:42:14 -0000 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. OK, I'm glad I asked. :-) Please take what you can from Sergey's patch, and credit him appropriately: http://ozz.pp.ru/patches/patch-pthread.2 There's a man page in there you should be able to use, at least. > 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. They're not allowed to return ENOTSUP. The Single Unix Specification says that if they're not implemented they must return success after doing nothing. John