From owner-freebsd-current Thu Mar 14 2:12:20 2002 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (esplanaden.cybercity.dk [212.242.40.114]) by hub.freebsd.org (Postfix) with ESMTP id A702E37B416 for ; Thu, 14 Mar 2002 02:12:17 -0800 (PST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.12.2/8.12.2) with ESMTP id g2EACFSr001355; Thu, 14 Mar 2002 11:12:15 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Alfred Perlstein Cc: David Greenman , John Indra , freebsd-current@FreeBSD.ORG Subject: Re: malloc() and the stock Perl in -CURRENT (and -STABLE) In-Reply-To: Your message of "Thu, 14 Mar 2002 02:03:03 PST." <20020314100303.GM74829@elvis.mu.org> Date: Thu, 14 Mar 2002 11:12:15 +0100 Message-ID: <1354.1016100735@critter.freebsd.dk> From: Poul-Henning Kamp 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 In message <20020314100303.GM74829@elvis.mu.org>, Alfred Perlstein writes: >> It would be much more valuable to add a >> mremap(void *from, void *to, size_t length); >> >> since that can _solve_ the problem in _all_ cases, rather than >> add more or less byzantine workarounds for silly benchmarks. > >You're right that it would be a better optimization, however it's >much more code to write than simply passing a flag down to the code >responsible for the allocation especially when you _know_ you'll >need it. Since when has going that extra mile to do it right been the wrong thing to do in FreeBSD ? :-) And everybody with VM clue I've asked says it would be trivial to flip two page-table entries, so for all I care it can be mexchangemapping(void *from, void *to, size_t length) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message