From owner-svn-src-head@FreeBSD.ORG Tue Feb 10 18:36:42 2015 Return-Path: Delivered-To: svn-src-head@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 31EFAEFA; Tue, 10 Feb 2015 18:36:42 +0000 (UTC) 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 E9D9F32F; Tue, 10 Feb 2015 18:36:41 +0000 (UTC) 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.14.9) with ESMTPSA id t1AIaSeb005471 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 10 Feb 2015 18:36:33 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 \(2070.6\)) Subject: Re: svn commit: r278479 - in head: etc sys/kern From: David Chisnall In-Reply-To: <8e5503e1-755c-49e4-ab4d-a0ad1ae91f97@me.com> Date: Tue, 10 Feb 2015 18:36:23 +0000 Content-Transfer-Encoding: quoted-printable Message-Id: <575FA8C1-0204-455C-A35A-787C48066AA5@FreeBSD.org> References: <8e5503e1-755c-49e4-ab4d-a0ad1ae91f97@me.com> To: Rui Paulo X-Mailer: Apple Mail (2.2070.6) Cc: "svn-src-head@freebsd.org" , Adrian Chadd , "src-committers@freebsd.org" , "svn-src-all@freebsd.org" , John Baldwin X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Feb 2015 18:36:42 -0000 On 10 Feb 2015, at 18:30, Rui Paulo wrote: >=20 > Another thing I had in mind (which is more work) was to abstract the = devctl kernel code in an API which could make it easy to fan out the = notifications to multiple /dev devices. However, that may be overkill. This kind of notification is something that kdbus is increasingly being = used for on Linux. The primitive allows events to originate either in = the kernel or in userspace and to be sent either point-to-point or to a = bloom filter set of recipients (so you occasionally get some messages = you're not expecting, but hopefully don't get too many spurious = wakeups). David