The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: David Howells <dhowells@cambridge.redhat.com>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: Kernel is unstable
Date: Fri, 2 Mar 2001 15:01:38 +0100	[thread overview]
Message-ID: <20010302150138.A18366@athlon.random> (raw)
In-Reply-To: <97m6ue$7uu$1@penguin.transmeta.com> <8165.983522444@warthog.cambridge.redhat.com>
In-Reply-To: <8165.983522444@warthog.cambridge.redhat.com>; from dhowells@cambridge.redhat.com on Fri, Mar 02, 2001 at 08:40:44AM +0000

On Fri, Mar 02, 2001 at 08:40:44AM +0000, David Howells wrote:
> no matter how finely optimised the algorithm... But merging wouldn't be done
> very often... only on memory allocation calls.

Correct, it would happen only at mmap time of course.

> Perhaps it'd be reasonable to only do VMA merging on mmap calls and not brk
> calls, and let brk manually extend an existing VMA if possible.

Yep.

Andrea

  reply	other threads:[~2001-03-02 14:01 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-01  9:16 Kernel is unstable Ivan Stepnikov
2001-03-01 10:27 ` Matti Aarnio
2001-03-01 14:35   ` Andrea Arcangeli
2001-03-01 14:39     ` Andrea Arcangeli
2001-03-01 18:20       ` Alan Cox
2001-03-01 18:30         ` Andrea Arcangeli
2001-03-01 19:04           ` David S. Miller
2001-03-01 20:45             ` Andrea Arcangeli
2001-03-01 19:12           ` Linus Torvalds
2001-03-02  8:23             ` Christoph Rohland
2001-03-02  8:40             ` David Howells
2001-03-02 14:01               ` Andrea Arcangeli [this message]
2001-03-02 17:52               ` Linus Torvalds
2001-03-05 23:06                 ` Chris Wedgwood
2001-03-01 13:39 ` Richard B. Johnson
2001-03-01 14:24 ` Andrea Arcangeli
2001-03-01 17:12   ` Ingo Oeser
  -- strict thread matches above, loose matches on Subject: below --
2001-03-01 13:55 Heusden, Folkert van

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=20010302150138.A18366@athlon.random \
    --to=andrea@suse.de \
    --cc=dhowells@cambridge.redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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