Date: Wed, 18 Dec 2002 05:24:03 +0900 From: Kyunghwan Kim <redjade@ada.snu.ac.kr> To: Andrew Gallatin <gallatin@cs.duke.edu> Cc: current@FreeBSD.ORG Subject: Re: INTR_MPSAFE to network device drivers Message-ID: <20021217202402.GA57385@ada.snu.ac.kr> In-Reply-To: <20021217195300.GB57094@ada.snu.ac.kr> References: <20021217191841.GA57094@ada.snu.ac.kr> <15871.31635.962334.855790@grasshopper.cs.duke.edu> <20021217195300.GB57094@ada.snu.ac.kr>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Dec 18, 2002 at 04:53:00AM +0900, Kyunghwan Kim wrote: > On Tue, Dec 17, 2002 at 02:31:31PM -0500, Andrew Gallatin wrote: > > > mbuf and bpf routines are all mp-safe, so it seems that > > > it is safe to make network device drivers out of Giant lock. > > > Or is there any unresolved related issues? > > > > Yes, the mbuf allocator must occasionally call kmem_malloc(), which > > requires Giant. This means no net driver can be made INTR_MPSAFE, > > or it will eventually panic when kmem_malloc is called. > > I found and read the thread that you and Alan had discussed about this > problem just before. Then what about making updated version of mb_pop_cont() > that accepts occasionally acquiring Giant? Oh, sorry. Conclusion of the thread was preallocation. But it doesn't seem that preallocation is the correct way. -- Kyunghwan Kim redjade@ada.snu.ac.kr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021217202402.GA57385>