linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: "David S. Miller" <davem@redhat.com>
Cc: sct@redhat.com, sim@stormix.com, jgarzik@mandrakesoft.com,
	riel@nl.linux.org, andrea@suse.de, linux-mm@kvack.org,
	bcrl@redhat.com, linux-kernel@vger.rutgers.edu
Subject: Re: [PATCH] 2.3.99-pre6-3+  VM rebalancing
Date: Wed, 26 Apr 2000 16:23:53 +0100	[thread overview]
Message-ID: <20000426162353.O3792@redhat.com> (raw)
In-Reply-To: <200004261311.GAA13838@pizda.ninka.net>; from davem@redhat.com on Wed, Apr 26, 2000 at 06:11:15AM -0700

Hi,

On Wed, Apr 26, 2000 at 06:11:15AM -0700, David S. Miller wrote:
> 
>    Doing it isn't the problem.  Doing it efficiently is, if you have 
>    fork() and mremap() in the picture.  With mremap(), you cannot assume
>    that the virtual address of an anonymous page is the same in all
>    processes which have the page mapped.
> 
> Who makes that assumption?

Nobody does --- that's the point.  If you _could_ make that assumption,
then looking up the vma which maps a given page in a given mm would be
easy.  But because the assumption doesn't hold, you have to walk all of
the vmas.

> In my implementation there is no linear scan, only VMA's which
> can actually contain the anonymous page in question are scanned.
> 
> It's called an anonymous layer, and it provides pseudo backing objects
> for VMA's which have at least one privatized anonymous page.
...

> Instead of talk, I'll show some code :-)  The following is the
> anon layer I implemented for 2.3.x in my hacks.

OK --- I'm assuming you allow all of these address spaces to act as 
swapper address spaces for the purpose of the swap cache?  This looks
good, do you have the rest of the VM changes in a usable (testable)
state?

On fork(), I assume you just leave multiple vmas attached to the same
address space?  With things like mprotect, you'll still have a list
of vmas to search for in this design, I'd think.

--Stephen
--
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.eu.org/Linux-MM/

  reply	other threads:[~2000-04-26 15:23 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-23  2:08 Rik van Riel
2000-04-25  1:25 ` Simon Kirby
2000-04-25 15:09   ` Rik van Riel
2000-04-25 15:59     ` Andrea Arcangeli
2000-04-25 17:20       ` Rik van Riel
2000-04-25 18:36         ` Simon Kirby
2000-04-25 18:59           ` Jeff Garzik
2000-04-25 19:06             ` Simon Kirby
2000-04-25 19:34               ` Rik van Riel
2000-04-26 11:01               ` Stephen C. Tweedie
2000-04-26 11:15                 ` Rik van Riel
2000-04-26 12:29                   ` Stephen C. Tweedie
2000-04-26 12:45                     ` David S. Miller
2000-04-26 11:25                 ` David S. Miller
2000-04-26 13:00                   ` Stephen C. Tweedie
2000-04-26 13:11                     ` David S. Miller
2000-04-26 15:23                       ` Stephen C. Tweedie [this message]
2000-04-26 15:25                         ` David S. Miller
2000-04-26 16:09                           ` Stephen C. Tweedie
2000-04-27 20:28                           ` Simon Kirby
2000-04-27 22:32                           ` Jamie Lokier
2000-04-26 13:46                   ` Rik van Riel
2000-04-26 14:33                     ` David S. Miller
2000-04-26 16:31                       ` Andi Kleen
2000-04-26 15:28                         ` David S. Miller
2000-04-26 15:41                           ` Andi Kleen

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=20000426162353.O3792@redhat.com \
    --to=sct@redhat.com \
    --cc=andrea@suse.de \
    --cc=bcrl@redhat.com \
    --cc=davem@redhat.com \
    --cc=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.rutgers.edu \
    --cc=linux-mm@kvack.org \
    --cc=riel@nl.linux.org \
    --cc=sim@stormix.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