From owner-freebsd-current@FreeBSD.ORG Mon Aug 5 15:35:46 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 989945A6 for ; Mon, 5 Aug 2013 15:35:46 +0000 (UTC) (envelope-from rdivacky@vlakno.cz) Received: from vlakno.cz (mail.vlakno.cz [178.238.39.38]) by mx1.freebsd.org (Postfix) with ESMTP id 5EB5E2385 for ; Mon, 5 Aug 2013 15:35:46 +0000 (UTC) Received: by vlakno.cz (Postfix, from userid 1002) id 2799B1CC5653; Mon, 5 Aug 2013 17:25:56 +0200 (CEST) Date: Mon, 5 Aug 2013 17:25:56 +0200 From: Roman Divacky To: Alfred Perlstein Subject: Re: Linux epoll(7) patch Message-ID: <20130805152556.GA37810@freebsd.org> References: <51FF7211.6020909@rawbw.com> <51FFC31D.3080304@mu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <51FFC31D.3080304@mu.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Yuri , current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Aug 2013 15:35:46 -0000 On Mon, Aug 05, 2013 at 08:22:05AM -0700, Alfred Perlstein wrote: > On 8/5/13 2:36 AM, Yuri wrote: > > There is the patch, suggested by Roman Divacky, implementing Linux > > epoll(7) functionality: > > http://rys.vlakno.cz/~rdivacky/patches/linux_epoll.patch > > > > This patch was suggested 5 years ago and was discussed on emulation@: > > http://lists.freebsd.org/pipermail/freebsd-emulation/2008-March/004409.html > > > > http://lists.freebsd.org/pipermail/freebsd-emulation/2008-March/004428.html > > > > > > Discussion stalled back then, and epoll is still unimplemented. > > > > Anybody can identify any issues with this patch? > > Are there any alternatives? > > > > Yuri > The patch is small. I too am wondering why it's not committed, was > there any push back? iirc the main problem with the patch is that it doesnt work over fork, I never got to implement that feature. Nevertheless it looks like the patch is useful even without that feature so maybe it should just be commited? Roman