From owner-freebsd-hackers@FreeBSD.ORG Sat Feb 2 23:17:53 2008 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 56CB716A421; Sat, 2 Feb 2008 23:17:53 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id F11C313C4E1; Sat, 2 Feb 2008 23:17:52 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 8C46D4B0E3; Sat, 2 Feb 2008 18:17:52 -0500 (EST) Date: Sat, 2 Feb 2008 23:17:52 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Alexander Motin In-Reply-To: <47A4F8EE.3070202@FreeBSD.org> Message-ID: <20080202231725.F66602@fledge.watson.org> References: <47A25412.3010301@FreeBSD.org> <47A25A0D.2080508@elischer.org> <47A2C2A2.5040109@FreeBSD.org> <20080201185435.X88034@fledge.watson.org> <47A43873.40801@FreeBSD.org> <20080202095658.R63379@fledge.watson.org> <47A4E934.1050207@FreeBSD.org> <47A4F1AF.9090306@FreeBSD.org> <20080202224923.T66602@fledge.watson.org> <47A4F8EE.3070202@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-hackers@freebsd.org, Kris Kennaway , freebsd-performance@freebsd.org, Julian Elischer Subject: Re: Memory allocation performance X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Feb 2008 23:17:53 -0000 On Sun, 3 Feb 2008, Alexander Motin wrote: > Robert Watson wrote: >> Basically, the goal would be to make the pcpu cache FIFO as much as >> possible as that maximizes the chances that the newly allocated object >> already has lines in the cache. > > Why FIFO? I think LIFO (stack) should be better for this goal as the last > freed object has more chances to be still present in cache. Sorry, brain-o -- indeed, as I described, LIFO, rather than as a I wrote. :-) Robert N M Watson Computer Laboratory University of Cambridge