Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 18 Nov 2002 20:38:38 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 18 Nov 2002 20:38:38 -0500 Received: from sccrmhc01.attbi.com ([204.127.202.61]:8340 "EHLO sccrmhc01.attbi.com") by vger.kernel.org with ESMTP id ; Mon, 18 Nov 2002 20:38:37 -0500 Message-ID: <3DD99D33.1030900@kegel.com> Date: Mon, 18 Nov 2002 18:08:51 -0800 From: Dan Kegel User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows 98) X-Accept-Language: de-de, en MIME-Version: 1.0 To: Davide Libenzi CC: Linux Kernel Mailing List Subject: Re: [rfc] epoll interface change and glibc bits ... References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1109 Lines: 30 Davide Libenzi wrote: > On Mon, 18 Nov 2002, Dan Kegel wrote: >>Second, epoll_ctl(2) doesn't define the meaning of the >>event mask. It should give the allowed bits and define >>their meanings. If we use the traditional POLLIN etc, we >>can say >> POLLIN - the fd has become ready for reading >> POLLOUT - the fd has become ready for writing >> Note: If epoll tells you e.g. POLLIN, it means that >> poll will tell you the same thing, >> since poll gives the current status, >> and epoll gives changes in status. > > > I will have to change man pages also to fit EPOLL* definitions. IMHO changing from using POLLIN etc. to EPOLLIN will obscure the essential relationship between epoll and poll (namely, that the epoll bits are the time derivative of the poll bits). I would prefer to continue using POLLIN, etc. - Dan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/