From owner-freebsd-current Wed Nov 4 16:15:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA10360 for freebsd-current-outgoing; Wed, 4 Nov 1998 16:15:34 -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 QAA10333 for ; Wed, 4 Nov 1998 16:15:23 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id LAA24698; Thu, 5 Nov 1998 11:22:36 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199811050022.LAA24698@cimlogic.com.au> Subject: Re: poll() for pthreads? In-Reply-To: <19981105005122.A13038@shale.csir.co.za> from Jeremy Lea at "Nov 5, 98 00:51:22 am" To: reg@shale.csir.co.za (Jeremy Lea) Date: Thu, 5 Nov 1998 11:22:36 +1100 (EST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL40 (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 Jeremy Lea wrote: > The CVS logs show that poll() is being hidden in libc_r because a > wrapper has not been written... However, this is way out of my league. > Does anyone have such a wrapper in their local tree, or is it a hard > thing to write? And would looking at the NSPR thread-safe wrapper for > poll() help? To implement poll(2) properly, the internal use of select(2) as the blocking mechanism needs to be changed to use poll. It's not just a matter of a wrapper, since you can implement true poll functionality with select. I thought Netscape were using their own threads. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ 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