From owner-freebsd-current Thu Mar 14 1:28:55 2002 Delivered-To: freebsd-current@freebsd.org Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by hub.freebsd.org (Postfix) with ESMTP id 060FA37B419 for ; Thu, 14 Mar 2002 01:28:48 -0800 (PST) Received: by elvis.mu.org (Postfix, from userid 1192) id D20A9AE1FC; Thu, 14 Mar 2002 01:28:47 -0800 (PST) Date: Thu, 14 Mar 2002 01:28:47 -0800 From: Alfred Perlstein To: Poul-Henning Kamp Cc: David Greenman , John Indra , freebsd-current@FreeBSD.ORG Subject: Re: malloc() and the stock Perl in -CURRENT (and -STABLE) Message-ID: <20020314092847.GL74829@elvis.mu.org> References: <20020313222518.J27616@nexus.root.com> <41161.1016088004@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41161.1016088004@critter.freebsd.dk> User-Agent: Mutt/1.3.27i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Poul-Henning Kamp [020313 22:43] wrote: > > But if somebody wants to try to code this optimization, I'll be more > than happy to review the result. I just don't expect it to do much > in "real-life" as opposed to "silly benchmark" situations. Have you thought about issuing a madvise(MADV_WILLNEED) after the brk/mmap call in malloc, at least doing it when it's called via realloc, this might get rid of the superfolous (sp?) page faults that David Greenman reported. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message