From owner-freebsd-hackers  Tue Oct  8 01:14:08 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id BAA07776
          for hackers-outgoing; Tue, 8 Oct 1996 01:14:08 -0700 (PDT)
Received: from critter.tfs.com ([140.145.230.252])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id BAA07768;
          Tue, 8 Oct 1996 01:14:03 -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 JAA03680; Tue, 8 Oct 1996 09:12:05 +0200 (MET DST)
To: Matt Thomas <matt@lkg.dec.com>
cc: hackers@freebsd.org, Mikael Karpberg <karpen@ocean.campus.luth.se>
Subject: Re: Optimizing bzero() 
In-reply-to: Your message of "Mon, 07 Oct 1996 17:07:59 -0000."
             <199610071708.RAA20621@whydos.lkg.dec.com> 
Date: Tue, 08 Oct 1996 09:12:05 +0200
Message-ID: <3678.844758725@critter.tfs.com>
From: Poul-Henning Kamp <phk@critter.tfs.com>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In message <199610071708.RAA20621@whydos.lkg.dec.com>, Matt Thomas writes:
>
>> > >Makes sense; can this be done without major surgery though? How costly 
>> > >would it be for malloc(3) to invoke a system call to re-arrange the
>> > >address space compared to an memory allocation followed by a bcopy()? 
>> > cheap(er).
>
>I've always wanted to be able to use procfs for doing that.  Alas, procfs
>doesn't support mmap operations.

Although I agree that it is a neat abstraction, I don't think I want to
involve the entire VFS system in this...

--
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.