From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Andrea Arcangeli <aarcange@redhat.com>,
lsf-pc@lists.linux-foundation.org
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-api@vger.kernel.org
Subject: Re: [LSF/MM TOPIC] userfaultfd
Date: Thu, 15 Jan 2015 11:08:28 -0500 [thread overview]
Message-ID: <54B7E5FC.3080006@gmail.com> (raw)
In-Reply-To: <20150114230130.GR6103@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 876 bytes --]
On 2015-01-14 18:01, Andrea Arcangeli wrote:
> 7) distributed shared memory that could allow simultaneous mapping of
> regions marked readonly and collapse them on the first exclusive
> write. I'm mentioning it as a corollary, because I'm not aware of
> anybody who is planning to use it that way (still I'd like that
> this will be possible too just in case it finds its way later on).
While I haven't actually written any code for it yet, I've been thinking
about the possibility to use this to allow qemu to do distributed
emulation of a NUMA system (ie, you could run qemu on a Beowulf cluster
and make it look to the guest OS like it's running on a big NUMA system,
essentially SSI clustering for people who don't have a multi-million
dollar budget). Having userfaultd to work with would make this
exponentially easier to implement.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 2455 bytes --]
prev parent reply other threads:[~2015-01-15 16:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 23:01 [LSF/MM TOPIC] userfaultfd Andrea Arcangeli
2015-01-15 9:01 ` Pavel Emelyanov
2015-01-15 16:08 ` Austin S Hemmelgarn [this message]
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=54B7E5FC.3080006@gmail.com \
--to=ahferroin7@gmail.com \
--cc=aarcange@redhat.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.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;
as well as URLs for NNTP newsgroup(s).