From owner-freebsd-arch@FreeBSD.ORG  Wed Sep 17 22:18:59 2003
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 6B98C16A4B3; Wed, 17 Sep 2003 22:18:59 -0700 (PDT)
Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 67EB643FB1; Wed, 17 Sep 2003 22:18:58 -0700 (PDT)
	(envelope-from imp@bsdimp.com)
Received: from localhost (warner@rover2.village.org [10.0.0.1])
	by harmony.village.org (8.12.9/8.12.3) with ESMTP id h8I5ImTX099857;
	Wed, 17 Sep 2003 23:18:49 -0600 (MDT)
	(envelope-from imp@bsdimp.com)
Date: Thu, 18 Sep 2003 06:17:07 -0600 (MDT)
Message-Id: <20030918.061707.115654192.imp@bsdimp.com>
To: bms@spc.org
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <20030918003556.GA1025@saboteur.dek.spc.org>
References: <20030917210236.GB75714@funkthat.com>
	<20030917201822.M55626-100000@mail.chesapeake.net>
	<20030918003556.GA1025@saboteur.dek.spc.org>
X-Mailer: Mew version 2.1 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
cc: rwatson@freebsd.org
cc: phk@phk.freebsd.dk
cc: gurney_j@efn.org
cc: freebsd-arch@freebsd.org
Subject: Re: devd limitations / automounting removable storage
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussion related to FreeBSD architecture
	<freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Sep 2003 05:18:59 -0000

In message: <20030918003556.GA1025@saboteur.dek.spc.org>
            Bruce M Simpson <bms@spc.org> writes:
: On Wed, Sep 17, 2003 at 08:18:49PM -0400, Jeff Roberson wrote:
: > On Wed, 17 Sep 2003, John-Mark Gurney wrote:
: > > I was thinking about a more generic event posting mechanism, where
: > > modules can register to receive notifications when events came in.
: > 
: > Please use kqueue.  We should have 1 eventing mechanism in the kernel.
: 
: Right now, the way devd/devctl works, it simply polls that device for changes.

No.  devctl gets an event queued to its read channel.  devd then reads
it.  That's different than polling for changes.

: Interesting. Are you suggesting we ditch /dev/devctl and define event
: filters instead inside NEWBUS? Assuming kqueue can be made to play with
: SMP and that we can push Giant out of it this might not be such a bad idea.

kqueue can report events. It can't transport arbitrary data, which is
what is needed here.

Warner