From owner-freebsd-current@freebsd.org Tue Jul 28 17:41:47 2015 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 6F1D79AC813 for ; Tue, 28 Jul 2015 17:41:47 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "cloud.theravensnest.org", Issuer "StartCom Class 1 Primary Intermediate Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 3599E14DE for ; Tue, 28 Jul 2015 17:41:46 +0000 (UTC) (envelope-from theraven@FreeBSD.org) Received: from [192.168.0.7] (cpc16-cmbg15-2-0-cust60.5-4.cable.virginm.net [86.5.162.61]) (authenticated bits=0) by theravensnest.org (8.15.1/8.15.1) with ESMTPSA id t6SHfffu039310 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 28 Jul 2015 17:41:43 GMT (envelope-from theraven@FreeBSD.org) X-Authentication-Warning: theravensnest.org: Host cpc16-cmbg15-2-0-cust60.5-4.cable.virginm.net [86.5.162.61] claimed to be [192.168.0.7] Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\)) Subject: Re: eventfd lookalike in FreeBSD ? From: David Chisnall In-Reply-To: Date: Tue, 28 Jul 2015 18:42:31 +0100 Cc: Luigi Rizzo , freebsd-current Content-Transfer-Encoding: quoted-printable Message-Id: References: <20150728121949.GA64588@onelab2.iet.unipi.it> <74DCC090-6AA7-43B8-81A1-DF66BC357489@FreeBSD.org> To: Adrian Chadd X-Mailer: Apple Mail (2.2098) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 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: Tue, 28 Jul 2015 17:41:47 -0000 On 28 Jul 2015, at 18:33, Adrian Chadd wrote: >=20 > Windows has had this for years. It makes async network programming > with thread worker queues significantly less abusive. Can you do the same with Solaris completion ports? It might be a good = source of inspiration for a good API if so. David