From owner-freebsd-arch Mon Jun 24 13:51:37 2002 Delivered-To: freebsd-arch@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [66.92.160.223]) by hub.freebsd.org (Postfix) with ESMTP id 3F96337B41C for ; Mon, 24 Jun 2002 13:51:29 -0700 (PDT) Received: from sasami.jurai.net (sasami.jurai.net [66.92.160.223]) by sasami.jurai.net (8.12.2/8.12.2) with ESMTP id g5OKpL2A096251; Mon, 24 Jun 2002 16:51:21 -0400 (EDT) (envelope-from winter@jurai.net) Date: Mon, 24 Jun 2002 16:51:21 -0400 (EDT) From: "Matthew N. Dodd" To: Poul-Henning Kamp Cc: "M. Warner Losh" , Subject: Re: It is time to admit that removable devices exist In-Reply-To: <83073.1024951336@critter.freebsd.dk> Message-ID: <20020624164822.H95270-100000@sasami.jurai.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 24 Jun 2002, Poul-Henning Kamp wrote: > When you eject a pccard, we may get in pccard-socket interrupt before it > disappears but we may also not. Depending on the world+dog this > interrupt me come before, during or after the relevant device driver > enters its interrupt routine. And dirtying up every bit of code that is called from the interrupt handler that touches the hardware isn't the solution. Thinking that this feature should actually work is the real problem. MacOS X and Windows don't support this (ie: they blow up just as often as we do when you try hot removing stuff.) I want to see the performance hit this causes quantified on lower end hardware before drivers are patched to support this API (which I concede may have some use outside PCMCIA devices.) -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message