From owner-freebsd-current@freebsd.org Wed Apr 27 10:32:40 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3C7A0B1ECFC for ; Wed, 27 Apr 2016 10:32:40 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 016ED1971; Wed, 27 Apr 2016 10:32:40 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1avMlp-000Fvb-Hm; Wed, 27 Apr 2016 13:32:37 +0300 Date: Wed, 27 Apr 2016 13:32:37 +0300 From: Slawa Olhovchenkov To: Julian Elischer Cc: freebsd-current Subject: Re: RFC on a published change to FreeBSD 11 kqueue file ops. Message-ID: <20160427103237.GL6614@zxy.spb.ru> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.21 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: Wed, 27 Apr 2016 10:32:40 -0000 On Wed, Apr 27, 2016 at 11:32:05AM +0800, Julian Elischer wrote: > the following change is sitting out at github, to add kqueue support > for more file operations: > > https://github.com/dmatveev/libinotify-kqueue/blob/master/patches > > does anyone have reasons why we shouldn't import this change. > > libinotify is now a port and could use these. Can you also see to kqueue and netmap interop?