From: "Ritchie, Stuart" <Stuart.Ritchie@tellabs.com>
To: Avi Kivity <avi@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Para-virtualized ram-based filesystem?
Date: Sun, 17 Apr 2011 22:28:14 -0500 [thread overview]
Message-ID: <C9D0FB51.BBB2%Stuart.Ritchie@tellabs.com> (raw)
In-Reply-To: <4DAAE05F.5050902@redhat.com>
On 4/17/11 5:43 AM, "Avi Kivity" <avi@redhat.com> wrote:
>On 04/16/2011 02:58 AM, Ritchie, Stuart wrote:
>> >
>> >You can do this with ivshmem today. You give it a path to a shared
>> >memory file, and then there's a path in sysfs that you can mmap() in
>> >userspace in the guest.
>>
>> Please correct me if I am wrong, but with ivshmem you must to manage
>>your
>> world within a single, fixed size region. I appreciate the simplicity
>>of
>> mapping the whole region all in one go, but our requirements are a bit
>> different. Even if you could pass multiple -device ivshmem instances,
>> it's still a fixed environment. Right?
>>
>
>You could place a read-only filesystem (say iso9660) in the region and
>mount it; it will then appear as a complete filesystem.
We've thought about formatting the region as a ramdisk, but the block
layer shields mmap() from the storage, thus requiring a data copy into the
page-cache. The great thing about ramfs/tmpfs is the data is used
in-place; we'd lose that when going with a ramdisk or other real
filesystem.
--Stuart
============================================================
The information contained in this message may be privileged
and confidential and protected from disclosure. If the reader
of this message is not the intended recipient, or an employee
or agent responsible for delivering this message to the
intended recipient, you are hereby notified that any reproduction,
dissemination or distribution of this communication is strictly
prohibited. If you have received this communication in error,
please notify us immediately by replying to the message and
deleting it from your computer. Thank you. Tellabs
============================================================
next prev parent reply other threads:[~2011-04-18 3:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-15 21:09 [Qemu-devel] Para-virtualized ram-based filesystem? Ritchie, Stuart
2011-04-15 21:43 ` Anthony Liguori
2011-04-15 23:58 ` Ritchie, Stuart
2011-04-16 0:27 ` Brad Hards
2011-04-16 8:52 ` Stefan Hajnoczi
2011-04-16 8:54 ` Stefan Hajnoczi
2011-04-18 4:12 ` Ritchie, Stuart
2011-04-17 12:43 ` Avi Kivity
2011-04-18 3:28 ` Ritchie, Stuart [this message]
2011-04-18 6:31 ` Avi Kivity
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=C9D0FB51.BBB2%Stuart.Ritchie@tellabs.com \
--to=stuart.ritchie@tellabs.com \
--cc=avi@redhat.com \
--cc=qemu-devel@nongnu.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).