From owner-freebsd-current Fri Feb 27 11:42:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA13678 for freebsd-current-outgoing; Fri, 27 Feb 1998 11:42:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA13668 for ; Fri, 27 Feb 1998 11:42:35 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.5/8.8.7) id GAA17389; Sat, 28 Feb 1998 06:43:52 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199802271943.GAA17389@cimlogic.com.au> Subject: Re: Pthreads in current In-Reply-To: <199802271329.NAA01214@chuggalug.clues.com> from Geoff Buckingham at "Feb 27, 98 01:29:14 pm" To: geoffb@chuggalug.clues.com (Geoff Buckingham) Date: Sat, 28 Feb 1998 06:43:52 +1100 (EST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Geoff Buckingham wrote: > Playing with yesterdays current I notice the aparent absence of > pthread_attr_setscope and pthread_attr_setschedparam from libc_r. pthread_attr_setscope depends on _POSIX_THREAD_PRIORITY_SCHEDULING which is commented out in pthread.h because there is currently no way to set a scheduling policy. > The man page claims both are present :-) This needs work. > pthread_setschedparam is also missing but I suspect this may be > non standard? (Although both Sun and SGI seem to have implimented it) > > Is this by intention or just that no one has implimented them yet? Yes and yes. 8-) -- John Birrell - jb@cimlogic.com.au; jb@netbsd.org; jb@freebsd.org CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message