mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Benjamin LaHaise <bcrl@redhat.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>, linux-kernel@vger.kernel.org
Subject: Re: Memory management in Kernel 2.4.x
Date: 27 May 2002 23:50:31 +0100	[thread overview]
Message-ID: <1022539831.4123.4.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <20020527173306.C15560@redhat.com>

On Mon, 2002-05-27 at 22:33, Benjamin LaHaise wrote:
> On Mon, May 27, 2002 at 02:22:22PM -0700, H. Peter Anvin wrote:
> > Well, if you can't fork a new process because that would push you into
> > overcommit, then you usually can't actually do anything useful on the
> > machine.
> 
> Just use vfork or clone + exec.  It's faster and uses less memory.

In the general case a fork doesn't cause too much overcommit. Most of
the binary is mapped read-only as is a lot of the library space. Since
its read only and backed by a file it has zero cost. If you mprotect it
then you pay at mprotect time


  parent reply	other threads:[~2002-05-27 21:47 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.iklie8v.5k2hbj@ifi.uio.no>
     [not found] ` <fa.na0lviv.e2a93a@ifi.uio.no>
2002-05-27 12:58   ` Andreas Hartmann
2002-05-27 13:45     ` Peter Wächtler
2002-05-27 15:25       ` Alan Cox
2002-05-27 14:37         ` Peter Wächtler
2002-05-27 21:22         ` H. Peter Anvin
2002-05-27 21:33           ` Benjamin LaHaise
2002-05-27 21:34             ` H. Peter Anvin
2002-05-27 21:37               ` Benjamin LaHaise
2002-05-27 21:39                 ` H. Peter Anvin
2002-05-27 22:50             ` Alan Cox [this message]
2002-05-27 21:56               ` William Lee Irwin III
2002-05-27 23:07                 ` Alan Cox
2002-05-27 22:48           ` Alan Cox
2002-06-05 13:33             ` Bill Davidsen
2002-05-31 21:19       ` Andrea Arcangeli
2002-06-01 12:35         ` Andreas Hartmann
2002-06-01 22:59           ` Andrea Arcangeli
2002-06-01 13:12         ` Andreas Hartmann
2002-06-03  8:11         ` Peter Wächtler
2002-05-28 14:46 Dmitry Volkoff
     [not found] <fa.n12rl6v.9644rg@ifi.uio.no>
     [not found] ` <fa.jd9c9pv.190gl8n@ifi.uio.no>
2002-05-28  5:42   ` Andreas Hartmann
2002-05-28 11:49     ` Alan Cox
2002-05-28 18:14       ` Andreas Hartmann
     [not found] <fa.huj8e2v.10ggghn@ifi.uio.no>
     [not found] ` <fa.o5cc8mv.12h4to1@ifi.uio.no>
2002-05-27 12:10   ` Andreas Hartmann
2002-05-27 11:52     ` Zwane Mwaikambo
  -- strict thread matches above, loose matches on Subject: below --
2002-05-27  9:40 Andreas Hartmann
2002-05-27 10:28 ` Florian Weimer
2002-05-27 12:02 ` Alan Cox

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1022539831.4123.4.camel@irongate.swansea.linux.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=bcrl@redhat.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®