linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Joseph A Knapka <jknapka@earthlink.net>
To: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
Cc: linux-mm@kvack.org
Subject: Re: Why *not* rmap, anyway?
Date: Sun, 21 Apr 2002 20:13:34 -0600	[thread overview]
Message-ID: <3CC371CE.1EE4E264@earthlink.net> (raw)
In-Reply-To: <3051330941.1019409833@[10.10.2.3]>

"Martin J. Bligh" wrote:
> 
> > I was just reading Bill's reply regaring rmap, and it
> > seems to me that rmap is the most obvious and clean
> > way to handle unmapping pages. So now I wonder why
> > it wasn't done that way from the beginning?
> 
> Because it costs something to maintain the reverse map.
> If the cost exceeds the benefit, it's not worth it. That's

Sure, but it's not obvious (is it?) that the rmap cost
exceeds the cost of scanning every process's virtual
address space looking for pages to unmap.

I'll have to look at the rmap patch and see. And
I gather that the *BSDs have always had reverse-
mappings, but thus far I haven't been able to
fathom the BSD code tree well enough to track down
on the VM code.

Thanks,

-- Joe
  Using open-source software: free.
  Pissing Bill Gates off: priceless.
--
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-22  2:13 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 [this message]
2002-04-22  5:46     ` Martin J. Bligh
2002-04-23 22:40     ` Christian Smith
2002-04-24  0:46       ` Rik van Riel
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=3CC371CE.1EE4E264@earthlink.net \
    --to=jknapka@earthlink.net \
    --cc=Martin.Bligh@us.ibm.com \
    --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