From owner-freebsd-current Sat Sep 26 10:05:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA24303 for freebsd-current-outgoing; Sat, 26 Sep 1998 10:05:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA24291 for ; Sat, 26 Sep 1998 10:05:29 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id KAA05259; Sat, 26 Sep 1998 10:52:32 -0600 (MDT) Date: Sat, 26 Sep 1998 10:52:32 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199809261652.KAA05259@narnia.plutotech.com> To: Poul-Henning Kamp cc: current@FreeBSD.ORG Subject: Re: Current is Really Broken(tm) Newsgroups: pluto.freebsd.current In-Reply-To: <7171.906791511@critter.freebsd.dk> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-BETA (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <7171.906791511@critter.freebsd.dk> you wrote: >>>This is just the idea that is realized by SLICE. >> >>This is exactly the opposite of what is realized by SLICE. SLICE >>does the "mount" at a deep level of the drivers (in an interrupt >>handler). > > ...Which was one of the most wrong things about it. Whatever replaces it must be able to be notified of insertion and removal events from an interrupt context. It can simply queue the notification up to be processed by a process or thread, but subsystems like CAM which process command completions from an SWI need to be able to perform notifications from low level contexts. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message