From owner-freebsd-smp Sun Jan 13 5: 8:39 2002 Delivered-To: freebsd-smp@freebsd.org Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by hub.freebsd.org (Postfix) with ESMTP id 92C8237B402; Sun, 13 Jan 2002 05:08:36 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1192) id 7A18110DDFC; Sun, 13 Jan 2002 05:08:36 -0800 (PST) Date: Sun, 13 Jan 2002 05:08:36 -0800 From: Alfred Perlstein To: smp@freebsd.org Cc: jhb@freebsd.org, dillon@freebsd.org Subject: making malloc(9) smp safe? Message-ID: <20020113050836.Q7984@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Malloc has its own mutex, however when it needs to do page allocations via kmem_malloc() it drops the mutex and calls it. kmem_malloc() needs giant. what do I do? Do I grab giant before calling malloc(9)? Do I make malloc(9) aquire or recurse on giant automatically? (basically grab giant around kmem_malloc() call in malloc(9)) ? -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' Tax deductable donations for FreeBSD: http://www.freebsdfoundation.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message