From owner-freebsd-hackers Mon Oct 16 12:40:08 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id MAA18378 for hackers-outgoing; Mon, 16 Oct 1995 12:40:08 -0700 Received: from expo.x.org (expo.x.org [198.112.45.11]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id MAA18373 for ; Mon, 16 Oct 1995 12:40:05 -0700 Received: from exalt.x.org by expo.x.org id AA29388; Mon, 16 Oct 95 15:39:33 -0400 Received: from localhost by exalt.x.org id PAA08113; Mon, 16 Oct 1995 15:39:30 -0400 Message-Id: <199510161939.PAA08113@exalt.x.org> To: Terry Lambert Cc: hackers@freefall.FreeBSD.org Subject: Re: getdtablesize() broken? In-Reply-To: Your message of Mon, 16 Oct 1995 11:31:02 EST. <199510161831.LAA25019@phaeton.artisoft.com> Organization: X Consortium Date: Mon, 16 Oct 1995 15:39:29 EST From: "Kaleb S. KEITHLEY" Sender: owner-hackers@FreeBSD.org Precedence: bulk >Poll, anyone? >Poll is inferior to select, Debatable. >both because of the 10ms limit on timeout >resoloution Man pages only say that if the host does not support millisecond accuracy then the value is rounded up to the nearest legal value available. >and because select is often used with no descriptors to >get a timeout and poll can't be used in this mode. That hasn't been my experience. poll(0, NULL, 10000); waits 10 seconds on SunOS, all SVR4-en I have here, HPUX, and AIX; however Digital Unix's poll looses. In fact in SVR4 select(3) is implemented using poll(2). In theory poll could be more efficient because there's less bit twiddling to do and unless you're polling thousands of files poll needs to transfer far less data to the kernel address space. Back in the days of 1.1.5.1 I started to look at what it would take to add poll. Maybe I'll look again. -- Kaleb