From: Stefan Hajnoczi <stefanha@gmail.com>
To: Stuart.Ritchie@tellabs.com
Cc: qemu-devel@nongnu.org, Brad Hards <bradh@frogmouth.net>
Subject: Re: [Qemu-devel] Para-virtualized ram-based filesystem?
Date: Sat, 16 Apr 2011 09:54:22 +0100 [thread overview]
Message-ID: <BANLkTikoRkA0fDThuPOKdg7W4rRp0w2TJg@mail.gmail.com> (raw)
In-Reply-To: <BANLkTin9uuAx7=X54L8D99+V_AiqHR_U4w@mail.gmail.com>
Resent because Stuart dropped from the recipients list.
On Sat, Apr 16, 2011 at 9:52 AM, Stefan Hajnoczi <stefanha@gmail.com> wrote:
> On Sat, Apr 16, 2011 at 1:27 AM, Brad Hards <bradh@frogmouth.net> wrote:
>> On Saturday 16 April 2011 09:58:32 Ritchie, Stuart wrote:
>>> How does that sound?
>> As a general user: Confusing.
>>
>> Is there a concrete example (specific applications, specific performance issues,
>> specific requirements) that you can share?
>
> I'm also wondering why you want this.
>
> Does it matter if the files get pushed out to swap on the host?
>
> It's tempting to take advantage of running virtualized but then things
> like migration get in the way. Have you actually tried out network
> file systems and determined they won't work for some reason?
>
> Stefan
>
next prev parent reply other threads:[~2011-04-16 8:54 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 [this message]
2011-04-18 4:12 ` Ritchie, Stuart
2011-04-17 12:43 ` Avi Kivity
2011-04-18 3:28 ` Ritchie, Stuart
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=BANLkTikoRkA0fDThuPOKdg7W4rRp0w2TJg@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=Stuart.Ritchie@tellabs.com \
--cc=bradh@frogmouth.net \
--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).