linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Lee Schermerhorn <lee.schermerhorn@hp.com>
To: Avi Kivity <avi@argo.co.il>
Cc: Paul Jackson <pj@sgi.com>, Christoph Lameter <clameter@sgi.com>,
	kamezawa.hiroyu@jp.fujitsu.com, linux-mm@kvack.org,
	Steve Ofsthun <sofsthun@virtualiron.com>
Subject: Re: [PATCH/RFC] AutoPage Migration - V0.1 - 0/8 Overview
Date: Wed, 15 Mar 2006 14:27:06 -0500	[thread overview]
Message-ID: <1142450826.5198.14.camel@localhost.localdomain> (raw)
In-Reply-To: <441863AC.6050101@argo.co.il>

On Wed, 2006-03-15 at 20:57 +0200, Avi Kivity wrote:
> Paul Jackson wrote:
> 
> >>a page if a certain mapcount is reached.
> >>    
> >>
> >
> >He said "accessed", not "referenced".
> >
> >The point was to copy pages that receive many
> >load and store instructions from far away nodes.
> >
> >  
> >
> Only loads, please. Writable pages should not be duplicated.
> 
> >This has only minimal to do with the number of
> >memory address spaces mapping the region
> >holding that page.
> >
> >  
> >
> 
> For starters, you could indicate which files need duplication manually. 
> You would duplicate your main binaries and associated shared objects. 
> Presumably large numas have plenty of memory so over-duplication would 
> not be a huge problem.
> 
> Is the kernel text duplicated?

No.  Might have been patches to do this for ia64 at one time.  I'm not
sure, tho'.

However, the folks at Virtual Iron do have patches to replicate shared,
executable segments.  They mentioned this at OLS last year.  I believe
that Ray Bryant got 'hold of a copy of the patch and had it working at
one time.  Didn't address one of the issues he was interested in, which
was to also duplicate the page tables for shared segments [?].  I hope
to experiment with them sometime down the line to see if they provide
measurable benefit.



--
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 19:27 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
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 [this message]
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=1142450826.5198.14.camel@localhost.localdomain \
    --to=lee.schermerhorn@hp.com \
    --cc=avi@argo.co.il \
    --cc=clameter@sgi.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-mm@kvack.org \
    --cc=pj@sgi.com \
    --cc=sofsthun@virtualiron.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