From: Christoph Lameter <clameter@sgi.com>
To: Paul Jackson <pj@sgi.com>
Cc: Avi Kivity <avi@argo.co.il>,
lee.schermerhorn@hp.com, kamezawa.hiroyu@jp.fujitsu.com,
linux-mm@kvack.org
Subject: Re: [PATCH/RFC] AutoPage Migration - V0.1 - 0/8 Overview
Date: Wed, 15 Mar 2006 10:10:26 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0603151008570.27212@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20060315095426.b70026b8.pj@sgi.com>
On Wed, 15 Mar 2006, Paul Jackson wrote:
> > Doesn't it make sense to duplicate heavily accessed shared read-only pages?
>
> It might .. that would be a major and difficult effort,
> and it is not clear that it would be a win. The additional
> bookkeeping to figure out what pages were heavily accessed
> would be very costly. Probably prohibitive.
>
> That's certainly a very different discussion than migration.
That is a different discussion but it is not complicated. There are
trivial one or two line patches around that make the fault handlers copy
a page if a certain mapcount is reached.
--
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>
next prev parent reply other threads:[~2006-03-15 18:10 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
2006-03-15 17:54 ` Paul Jackson
2006-03-15 18:10 ` Christoph Lameter [this message]
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=Pine.LNX.4.64.0603151008570.27212@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=avi@argo.co.il \
--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