Date: Tue, 15 Oct 2002 14:45:13 -0400 (EDT) From: Andrew Gallatin <gallatin@cs.duke.edu> To: freebsd-arch@freebsd.org Subject: when will malloc(9) be giant-free? Message-ID: <15788.25145.767671.511786@grasshopper.cs.duke.edu>
next in thread | raw e-mail | index | archive | help
I'm trying to call malloc from a mostly giant-free driver, and dying like this: panic(c0346b0e,c0346c57,c03584e6,138,c037caa0) at panic+0x11f _mtx_assert(c037cc60,1,c03584e6,138,158) at _mtx_assert+0xbc kmem_malloc(c0832078,21000,1,d8e287ec,c02db8ea) at kmem_malloc+0x2d page_alloc(0,21000,d8e287df,1,23459e4) at page_alloc+0x27 uma_large_malloc(21000,1,c02db064,6,c4435cfc) at uma_large_malloc+0x5a malloc(20fff,c037af20,1,d8e2883c,c4741873) at malloc+0xcd __gm_arch_kernel_malloc(20fff,0,d8e2884c,c47435d1,20fff) at __gm_arch_kernel_malloc+0x12 So, yes, I'll grab giant around calls to malloc and free, but when do we anticipate that kmem_malloc() will be giant-free? Yes, I whined about this a few months ago in relation to mbuf allocation at interrupt time (I was porting the ethernet emulation side of our driver to -current). Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15788.25145.767671.511786>