From: Jack Steiner <steiner@sgi.com>
To: Lee Schermerhorn <lee.schermerhorn@hp.com>
Cc: Avi Kivity <avi@argo.co.il>, 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 13:56:55 -0600 [thread overview]
Message-ID: <20060315195654.GA16771@sgi.com> (raw)
In-Reply-To: <1142450826.5198.14.camel@localhost.localdomain>
> > Is the kernel text duplicated?
>
> No. Might have been patches to do this for ia64 at one time. I'm not
> sure, tho'.
>
Yes, there is a patch to duplicate kernel text. I still have a copy
although I'm sure it has gotten very stale.
Kernel text replication was part of the IA64 "trillian" patch at
one time but was dropped because we never saw any significant benefit.
However, systems are larger now & I would not be surprised if
replication helped on very large systems.
I plan to retest kernel replication within the next couple of
months. Stay tuned...
---
Jack
--
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 19:56 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
2006-03-15 19:56 ` Jack Steiner [this message]
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=20060315195654.GA16771@sgi.com \
--to=steiner@sgi.com \
--cc=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 \
--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