Date: Thu, 02 May 2002 10:16:25 -0400 (EDT) From: John Baldwin <jhb@FreeBSD.org> To: Jeff Roberson <jeff@FreeBSD.org> Cc: cvs-all@FreeBSD.org, cvs-committers@FreeBSD.org Subject: RE: cvs commit: src/sys/kern kern_malloc.c src/sys/vm uma_core.c Message-ID: <XFMail.20020502101625.jhb@FreeBSD.org> In-Reply-To: <200205020722.g427MJM10914@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 02-May-2002 Jeff Roberson wrote: > jeff 2002/05/02 00:22:19 PDT > > Modified files: > sys/kern kern_malloc.c > sys/vm uma_core.c uma_dbg.c > sys/sys malloc.h > Log: > malloc/free(9) no longer require Giant. Use the malloc_mtx to protect the > mallochash. Mallochash is going to go away as soon as I introduce the > kfree/kmalloc api and partially overhaul the malloc wrapper. This can't > happen > until all users of the malloc api that expect memory to be aligned on the > size > of the allocation are fixed. Can malloc() still block and still possibly obtain Giant internally? If so, malloc() should still not be called with other locks held. -- John Baldwin <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.20020502101625.jhb>