Date: Wed, 05 Feb 2003 12:15:21 +0100 From: Dag-Erling Smorgrav <des@ofug.org> To: David Schultz <dschultz@uclink.Berkeley.EDU> Cc: arch@freebsd.org Subject: Re: New kernel allocation API Message-ID: <xzpznpbq8qe.fsf@flood.ping.uio.no> In-Reply-To: <20030205045103.GB2168@HAL9000.homeunix.com> (David Schultz's message of "Tue, 4 Feb 2003 20:51:03 -0800") References: <xzp8ywvs6yu.fsf@flood.ping.uio.no> <xzp65rzs6ry.fsf@flood.ping.uio.no> <20030205045103.GB2168@HAL9000.homeunix.com>
next in thread | previous in thread | raw e-mail | index | archive | help
David Schultz <dschultz@uclink.Berkeley.EDU> writes: > BTW, it looks like the KASSERT in kalloc() eliminates the need for > the one in malloc(). Furthermore, there's another KASSERT in > malloc() that could be moved to kalloc(). I know. AT this stage, all the patch does is define the new API and implement it in terms of the old one. I duplicated the KASSERT so I could tailor the panic string to the new API. Note that since malloc() still exists and is not static, the patch maintains binary compatibility (e.g. with modules compiled before the patch was applied). It would therefore have been wrong to modify the behaviour of malloc(). DES -- Dag-Erling Smorgrav - des@ofug.org 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?xzpznpbq8qe.fsf>