From owner-freebsd-hackers Sun Jan 26 03:37:42 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id DAA02826 for hackers-outgoing; Sun, 26 Jan 1997 03:37:42 -0800 (PST) Received: from parkplace.cet.co.jp (parkplace.cet.co.jp [202.32.64.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA02821 for ; Sun, 26 Jan 1997 03:37:40 -0800 (PST) Received: from localhost (michaelh@localhost) by parkplace.cet.co.jp (8.8.3/CET-v2.1) with SMTP id LAA21972; Sun, 26 Jan 1997 11:36:44 GMT Date: Sun, 26 Jan 1997 20:36:44 +0900 (JST) From: Michael Hancock To: proff@suburbia.net cc: hackers@freebsd.org Subject: Re: SLAB stuff, and applications to current net code (fwd) In-Reply-To: <19970126042316.10096.qmail@suburbia.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sun, 26 Jan 1997 proff@suburbia.net wrote: > Can anyone inform me what a SLAB allocator is, and if so, would freebsd > benefit from one? > It's a chunk of memory that you put multiple kernel objects of the same type into. We have a modified mach zone allocator. They're both type stable memory allocators. Maybe John or David will explain how our allocator differs from the original zone allocator in 4.4BSD borrowed from Mach. I not sure how much benefit the SLAB allocator would offer over what we have. There's some extra overhead in maintaining a SLAB. BTW, SLAB is used in Solaris. Regards, Mike Hancock