From owner-freebsd-hackers@FreeBSD.ORG Mon Nov 3 02:59:34 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1F36316A4CE for ; Mon, 3 Nov 2003 02:59:34 -0800 (PST) Received: from arginine.spc.org (arginine.spc.org [195.206.69.236]) by mx1.FreeBSD.org (Postfix) with ESMTP id EB76F43FAF for ; Mon, 3 Nov 2003 02:59:32 -0800 (PST) (envelope-from bms@spc.org) Received: from localhost (localhost [127.0.0.1]) by arginine.spc.org (Postfix) with ESMTP id B8F836542D; Mon, 3 Nov 2003 10:59:31 +0000 (GMT) Received: from arginine.spc.org ([127.0.0.1]) by localhost (arginine.spc.org [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 56731-01; Mon, 3 Nov 2003 10:59:31 +0000 (GMT) Received: from saboteur.dek.spc.org (unknown [82.147.19.91]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by arginine.spc.org (Postfix) with ESMTP id A03166542C; Mon, 3 Nov 2003 10:59:30 +0000 (GMT) Received: by saboteur.dek.spc.org (Postfix, from userid 1001) id A42BD40; Mon, 3 Nov 2003 10:59:29 +0000 (GMT) Date: Mon, 3 Nov 2003 10:59:29 +0000 From: Bruce M Simpson To: Gerald Heinig Message-ID: <20031103105929.GB17479@saboteur.dek.spc.org> References: <3FA6253E.9D727094@syskonnect.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3FA6253E.9D727094@syskonnect.de> cc: hackers@freebsd.org Subject: Re: kernel malloc usage X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Nov 2003 10:59:34 -0000 On Mon, Nov 03, 2003 at 10:51:58AM +0100, Gerald Heinig wrote: > Is this true? I seem to remember that FreeBSD has a slab allocator, > which IIRC is particularly good at allocating small chunks. You don't specify which version of the kernel you're programming to; so I'll assume 5.x. If your allocations are of similar size, then consider using the zone allocator; I believe this implements a slab-like algorithm. BMS