linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@argo.co.il>
To: Christoph Lameter <clameter@sgi.com>
Cc: Lee Schermerhorn <lee.schermerhorn@hp.com>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	linux-mm@kvack.org, pj@sgi.com
Subject: Re: [PATCH/RFC] AutoPage Migration - V0.1 - 0/8 Overview
Date: Wed, 15 Mar 2006 18:05:56 +0200	[thread overview]
Message-ID: <44183B64.3050701@argo.co.il> (raw)
In-Reply-To: <Pine.LNX.4.64.0603131541330.13713@schroedinger.engr.sgi.com>

Christoph Lameter wrote:

>cpusets uses _MOVE_ALL because Paul wanted it that way. I still think it 
>is a bad idea to move shared libraries etc. _MOVE only moves the pages used
>by the currently executing process. If you do a MOVE_ALL then you may 
>cause delays in other processes because they have to wait for their pages 
>to become available again. Also they may have to generate additional 
>faults to restore their PTEs. So you are negatively impacting other 
>processes. Note that these wait times can be extensive if _MOVE_ALL is 
>f.e. just migrating a critical glibc page that all processes use.
>  
>
Doesn't it make sense to duplicate heavily accessed shared read-only pages?

Something like page migration, but keeping the original page intact. 
Unfortunately, for threaded applications, it means page table bases 
(cr3) can't be shared among threads.

-- 
error compiling committee.c: too many arguments to function

--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2006-03-15 16:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-10 19:33 Lee Schermerhorn
2006-03-11  6:41 ` KAMEZAWA Hiroyuki
2006-03-13 17:27   ` Lee Schermerhorn
2006-03-13 23:45     ` Christoph Lameter
2006-03-15 16:05       ` Avi Kivity [this message]
2006-03-15 17:54         ` Paul Jackson
2006-03-15 18:10           ` Christoph Lameter
2006-03-15 18:14             ` Paul Jackson
2006-03-15 18:20               ` Christoph Lameter
2006-03-15 19:21                 ` Lee Schermerhorn
2006-03-15 18:57               ` Avi Kivity
2006-03-15 19:27                 ` Lee Schermerhorn
2006-03-15 19:56                   ` Jack Steiner
2006-03-14 22:27 ` Lee Schermerhorn

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=44183B64.3050701@argo.co.il \
    --to=avi@argo.co.il \
    --cc=clameter@sgi.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=lee.schermerhorn@hp.com \
    --cc=linux-mm@kvack.org \
    --cc=pj@sgi.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