From owner-freebsd-arch Tue Oct 15 11:45:45 2002 Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E626337B401 for ; Tue, 15 Oct 2002 11:45:44 -0700 (PDT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 554F643EB3 for ; Tue, 15 Oct 2002 11:45:44 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id OAA12141 for ; Tue, 15 Oct 2002 14:45:43 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g9FIjDX55815; Tue, 15 Oct 2002 14:45:13 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15788.25145.767671.511786@grasshopper.cs.duke.edu> Date: Tue, 15 Oct 2002 14:45:13 -0400 (EDT) To: freebsd-arch@freebsd.org Subject: when will malloc(9) be giant-free? X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid 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 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