Date: Wed, 31 Jul 2002 21:12:35 -0500 From: Alan Cox <alc@cs.rice.edu> To: Andrew Gallatin <gallatin@cs.duke.edu> Cc: Peter Wemm <peter@wemm.org>, John Baldwin <jhb@FreeBSD.org>, freebsd-smp@FreeBSD.org Subject: Re: INTR_MPSAFE network drivers Message-ID: <20020801021235.GD9934@cs.rice.edu> In-Reply-To: <15688.22002.772933.316104@grasshopper.cs.duke.edu> References: <XFMail.20020729175342.jhb@FreeBSD.org> <20020730000345.E0D9F2A7D6@canning.wemm.org> <15686.48913.150407.307190@grasshopper.cs.duke.edu> <20020730171226.GA26599@cs.rice.edu> <15688.22002.772933.316104@grasshopper.cs.duke.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jul 31, 2002 at 05:26:10PM -0400, Andrew Gallatin wrote: > > For what its worth, this *seems* to work OK on a non-WITNESS, > non-INVARIENTs kernel. > That's what I would expect. The difficult problem that we'll have with kmem_malloc() and friends stems from legacy drivers that rely on Giant, not a properly locked driver. If a legacy driver sleeps because kmem_malloc() is unable to acquire the mb_map or kernel_map lock, they may wake up to an inconsistent state. Right now, requiring Giant in the top half of the kernel to call kmem_malloc() et al. prevents this. Alan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020801021235.GD9934>