linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Rik van Riel <riel@conectiva.com.br>
To: Christian Smith <csmith@micromuse.com>
Cc: Joseph A Knapka <jknapka@earthlink.net>,
	"Martin J. Bligh" <Martin.Bligh@us.ibm.com>,
	linux-mm@kvack.org
Subject: Re: Why *not* rmap, anyway?
Date: Tue, 23 Apr 2002 21:46:20 -0300 (BRT)	[thread overview]
Message-ID: <Pine.LNX.4.44L.0204232145120.1960-100000@imladris.surriel.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0204232317320.1968-100000@erol>

On Tue, 23 Apr 2002, Christian Smith wrote:

> The question becomes, how much work would it be to rip out the Linux MM
> piece-meal, and replace it with an implementation of UVM?

I doubt we want the Mach pmap layer.

It should be much easier to reimplement the pageout parts of
the BSD memory management on top of a simpler reverse mapping
system.

You can get that code at  http://surriel.com/patches/

cheers,

Rik
-- 
Bravely reimplemented by the knights who say "NIH".

http://www.surriel.com/		http://distro.conectiva.com/

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/

  reply	other threads:[~2002-04-24  0:46 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-21 22:27 Joseph A Knapka
2002-04-22  0:23 ` Martin J. Bligh
2002-04-22  2:13   ` Joseph A Knapka
2002-04-22  5:46     ` Martin J. Bligh
2002-04-23 22:40     ` Christian Smith
2002-04-24  0:46       ` Rik van Riel [this message]
2002-04-24 10:50         ` Christian Smith
2002-04-24 14:20           ` Rik van Riel
2002-04-24 14:37             ` Momchil Velikov
2002-04-24 14:52               ` Rik van Riel
2002-04-24 15:16                 ` Momchil Velikov
2002-04-24 18:31                   ` William Lee Irwin III
2002-04-25 15:19             ` Christian Smith
2002-05-05 19:04           ` Daniel Phillips
2002-05-07 18:37             ` Christian Smith
2002-05-07 19:23               ` Rik van Riel
2002-05-07 19:25                 ` William Lee Irwin III
2002-05-07 19:47                   ` Daniel Phillips
2002-05-07 19:50                     ` William Lee Irwin III
2002-05-07 23:02                       ` Daniel Phillips
2002-05-08  0:08                         ` William Lee Irwin III
2002-05-08  5:08                           ` Andrew Morton
2002-05-08  7:59                     ` Momchil Velikov
2002-05-08 14:33                       ` Daniel Phillips
2002-05-08 14:43                         ` Rik van Riel
2002-05-08 16:06                           ` Daniel Phillips
2002-05-08 16:10                             ` Rik van Riel
2002-05-07 19:49                   ` Rik van Riel
2002-05-07 19:53                     ` William Lee Irwin III
2002-05-07 19:43                 ` Daniel Phillips
2002-05-07 19:51                   ` Rik van Riel
2002-05-07 23:11                     ` Daniel Phillips
2002-05-07 21:21                   ` William Lee Irwin III
2002-05-07 23:15                     ` Daniel Phillips
2002-05-07 19:37               ` Daniel Phillips
2002-05-07 19:47                 ` William Lee Irwin III
2002-05-05 18:38         ` Daniel Phillips
2002-05-05 22:23           ` Rik van Riel

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=Pine.LNX.4.44L.0204232145120.1960-100000@imladris.surriel.com \
    --to=riel@conectiva.com.br \
    --cc=Martin.Bligh@us.ibm.com \
    --cc=csmith@micromuse.com \
    --cc=jknapka@earthlink.net \
    --cc=linux-mm@kvack.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