From owner-freebsd-hackers Mon Sep 30 04:45:58 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id EAA00346 for hackers-outgoing; Mon, 30 Sep 1996 04:45:58 -0700 (PDT) Received: from critter.tfs.com ([140.145.230.252]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id EAA00278; Mon, 30 Sep 1996 04:45:53 -0700 (PDT) Received: from critter.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.7.5/8.7.3) with ESMTP id NAA08052; Mon, 30 Sep 1996 13:45:13 +0200 (MET DST) To: Mikael Karpberg cc: hackers@FreeBSD.ORG Subject: Re: Optimizing bzero() In-reply-to: Your message of "Mon, 30 Sep 1996 10:33:14 +0200." <199609300833.KAA18915@ocean.campus.luth.se> Date: Mon, 30 Sep 1996 13:45:12 +0200 Message-ID: <8050.844083912@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message <199609300833.KAA18915@ocean.campus.luth.se>, Mikael Karpberg writes >> > >> >phk> The next thing you could start to consider is when people realloc a >> >phk> multipage allocation to something bigger, it would be nice to be able >> >phk> to ask the kernel to "move these pages to this address" and then exten >d >> >phk> It there instead of copying the contents. >> > >Can't you just make realloc do that? Is there a problem with doing it? >If not, is there a way to tell the system to rearrange your address space? It would be done in realloc(), but the savings seems to be very marginal from the traces I have collected so far. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@ref.tfs.com TRW Financial Systems, Inc. Future will arrive by its own means, progress not so.