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: Sun, 13 Jan 2008 06:09:39 -0600	[thread overview]
Message-ID: <20080113120939.GA3221@sgi.com> (raw)
In-Reply-To: <47891A5C.8060907@qumranet.com>

On Sat, Jan 12, 2008 at 09:51:56PM +0200, Avi Kivity wrote:
> Christoph Lameter wrote:
>> On Thu, 10 Jan 2008, Avi Kivity wrote:
>>
>>   
>>> 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?
>>>     
>>
>> A file from where? If a file is read by two guests then they will have 
>> distinct page structs.
>>
>>   
>
> Two kvm instances mmap() the file (from anywhere) into the guest address 
> space.  That memory is shared, and will be backed by the same page structs 
> at the same offset.

That sounds nice, but...

For larger machine configurations, we have different memory access
capabilities.  When a partition that is located close to the home node
of the memory accesses memory, it is normal access.  When it is further
away, they get special access to the line.  Before the shared line is
sent to the reading node, it is converted by the memory controller into
an exclusive request and the reading node is handed the only copy of
the line.  If we gave a remote kernel access to the page, we would also
open the entire owning nodes page tables up to speculative references
which effectively would be viewed by hardware as cache-line contention.

Additionally, we have needs beyond memory backed by files.  Including
special devices which do not have struct pages at all (see mspec.c).

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-13 12:09 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
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 [this message]
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=20080113120939.GA3221@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