From owner-freebsd-hackers Fri Apr 4 09:44:22 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA21960 for hackers-outgoing; Fri, 4 Apr 1997 09:44:22 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id JAA21952 for ; Fri, 4 Apr 1997 09:44:15 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id KAA19477; Fri, 4 Apr 1997 10:26:19 -0700 From: Terry Lambert Message-Id: <199704041726.KAA19477@phaeton.artisoft.com> Subject: Re: new malloc To: dg@root.com Date: Fri, 4 Apr 1997 10:26:18 -0700 (MST) Cc: borjam@we.lc.ehu.es, freebsd-hackers@freebsd.org In-Reply-To: <199704041027.CAA10928@root.com> from "David Greenman" at Apr 4, 97 02:27:01 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Of course, the same idea cn be applied adding a MRU policy to the > >allocation routine. > > Both Poul-Henning's and the FreeBSD kernel's malloc allocate and insert > chunks at the head of the free queue - thus they already are LIFO. I assume this is for things with zero locality of reference (ie: no second chancing, etc.)? Regards, Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.