linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Robin Holt <holt@sgi.com>
To: Avi Kivity <avi@qumranet.com>
Cc: Christoph Lameter <clameter@sgi.com>,
	Andrea Arcangeli <andrea@qumranet.com>,
	kvm-devel@lists.sourceforge.net, linux-mm@kvack.org,
	Daniel J Blueman <daniel.blueman@quadrics.com>
Subject: Re: [kvm-devel] mmu notifiers
Date: Thu, 10 Jan 2008 07:16:12 -0600	[thread overview]
Message-ID: <20080110131612.GA1933@sgi.com> (raw)
In-Reply-To: <47860512.3040607@qumranet.com>

On Thu, Jan 10, 2008 at 01:44:18PM +0200, Avi Kivity wrote:
> Christoph Lameter wrote:
>> On Wed, 9 Jan 2008, Andrea Arcangeli wrote:
>>
>>   
>>> This patch is a first basic implementation of the mmu notifiers. More
>>> methods can be added in the future.
>>>
>>> In short when the linux VM decides to free a page, it will unmap it
>>> from the linux pagetables. However when a page is mapped not just by
>>> the regular linux ptes, but also from the shadow pagetables, it's
>>> currently unfreeable by the linux VM.
>>>     
>>
>> Such a patch would also address issues that SGI has with exporting 
>> mappings via XPMEM. Plus a variety of other uses. Go ahead and lets do 
>> more in this area.
>>
>> Are the KVM folks interested in exporting memory from one guest to 
>> another? That may also become possible with some of the work that we have 
>> in progress and that also requires a patch like this.
>>
>>   
>
> Actually sharing memory is possible even without this patch; one simply 
> mmap()s a file into the address space of both guests.  Or are you referring 
> to something else?

He is referring to the xpmem work SGI has pushed in the past.  It was
rejected precisely because this type functionality did not exist.  We were
trying to determine the cleanest yet smallest acceptable implementation
when this suddenly sprang up.  I would expect Dean Nelson or myself to
repost the xpmem patch set again based upon this patche.

> The patch does enable some nifty things; one example you may be familiar 
> with is using page migration to move a guest from one numa node to another.

xpmem allows one MPI rank to "export" his address space, a different
MPI rank to "import" that address space, and they share the same pages.
This allows sharing of things like stack and heap space.  XPMEM also
provides a mechanism to share that PFN information across partition
boundaries so the pages become available on a different host.  This,
of course, is dependent upon hardware that supports direct access to
the memory by the processor.

Thanks,
Robin

--
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:[~2008-01-10 13:16 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-09 18:19 Andrea Arcangeli
2008-01-09 21:54 ` Christoph Lameter
2008-01-10 11:44   ` [kvm-devel] " Avi Kivity
2008-01-10 13:16     ` Robin Holt [this message]
2008-01-10 13:27       ` Avi Kivity
2008-01-10 14:50         ` Robin Holt
2008-01-10 19:06         ` Christoph Lameter
2008-01-12 19:56           ` Avi Kivity
2008-01-10 19:04     ` Christoph Lameter
2008-01-12 19:51       ` Avi Kivity
2008-01-13 12:09         ` Robin Holt
2008-01-13 12:28           ` Avi Kivity
2008-01-14 19:51             ` Christoph Lameter
2008-01-15  7:43               ` Avi Kivity
2008-01-14 19:49         ` Christoph Lameter
2008-01-15  7:38           ` Avi Kivity
2008-01-15 17:39             ` Christoph Lameter
2008-01-15 17:53               ` Avi Kivity
2008-01-15 17:57                 ` Christoph Lameter
2008-01-15 18:06                   ` Avi Kivity
2008-01-15 18:16                     ` Christoph Lameter
2008-01-16  7:39                       ` Avi Kivity
2008-01-16 18:08                         ` Christoph Lameter

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=20080110131612.GA1933@sgi.com \
    --to=holt@sgi.com \
    --cc=andrea@qumranet.com \
    --cc=avi@qumranet.com \
    --cc=clameter@sgi.com \
    --cc=daniel.blueman@quadrics.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=linux-mm@kvack.org \
    /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