From owner-freebsd-questions Wed Mar 15 22:05:36 1995 Return-Path: questions-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id WAA01271 for questions-outgoing; Wed, 15 Mar 1995 22:05:36 -0800 Received: from omega.uta.edu (omega.uta.edu [129.107.1.23]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id WAA01265 for ; Wed, 15 Mar 1995 22:05:34 -0800 Received: (from nguyen@localhost) by omega.uta.edu (8.6.9/8.6.9) id AAA00657 for freebsd-questions@FreeBSD.org; Thu, 16 Mar 1995 00:05:32 -0600 From: TR Nguyen Message-Id: <199503160605.AAA00657@omega.uta.edu> Subject: Asynch I/O: poll(2)/select(2) To: freebsd-questions@FreeBSD.org Date: Thu, 16 Mar 1995 00:05:32 -0600 (CST) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1073 Sender: questions-owner@FreeBSD.org Precedence: bulk Hello everyone, I think this is more of a developmental issue than anything else. On SystemV unices, the system call poll(2) is used for multiple file descriptor polling, and select(2) is implemented on top of poll(2). I'm used to the Alpha runing OSF/1 (POSIX compliant). For many reasons I've always preferred poll(2) over select(2) When porting my code to FreeBSD, I wrote my own version of poll by translating poll(2)'s argument to select()'s format. call select(2) to poll my file descriptors, then translate select(2)'s result back to the format used by poll(2). This works fine, but I'm wondering if someone did this before. I would appreciate some examples (other than my own), preferably a kernel-level implementation, rather than at the Programmer Interface Level (API). I'm very interested in the most efficient implementation possible. I am aware that FreeBSD is striving to become POSIX compliant. (1003.1? 1003.4?) Anyone out there with some knowlege/rumor to share? Thank. TR Nguyen PS. I apologize for not posting to the developmental-related list.