From: Laszlo Ersek <lersek@redhat.com>
To: josh@joshtriplett.org
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Michael Tsirkin" <mtsirkin@redhat.com>,
edk2-devel-01 <edk2-devel@ml01.01.org>,
"Shannon Zhao" <zhaoshenglong@huawei.com>,
"qemu devel list" <qemu-devel@nongnu.org>,
"Moore, Robert" <robert.moore@intel.com>,
"Smith, Jonathan D" <jonathan.d.smith@intel.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Marcel Apfelbaum" <marcel@redhat.com>,
"Igor Mammedov" <imammedo@redhat.com>,
"Marc Marí" <markmb@redhat.com>, "Jake Edge" <jake@lwn.net>,
"Gabriel L. Somlo (CMU)" <somlo@cmu.edu>
Subject: Re: [Qemu-devel] "Using Python to investigate EFI and ACPI"
Date: Fri, 4 Sep 2015 01:21:57 +0200 [thread overview]
Message-ID: <55E8D615.5070808@redhat.com> (raw)
In-Reply-To: <20150903212504.GA24388@cloud>
On 09/03/15 23:25, josh@joshtriplett.org wrote:
> On Thu, Sep 03, 2015 at 07:19:40PM +0200, Laszlo Ersek wrote:
>> In any case, if what you need resembles a "general virtio filesystem",
>> then please just use that -- a virtio-block or virtio-scsi disk, with a
>> normal filesystem on it. The protocol is industry standard and the
>> performance of the QEMU (and kernel) implementation is splendid.
>
> Not at all what I'm looking for; I'm looking for a *filesystem*, like
> virtio-9p, but with significantly better performance. I agree that
> starting from fw_cfg for that is probably a bad idea; it's more that if
> a high-performance virtio filesystem existed, it might also work for
> fw_cfg. :)
Thanks for mentioning "virtio-9p", now I remember what to point at
instead of it. I recommend Stefan's slides from this year's KVM forum.
https://kvmforum2015.sched.org/event/bca50b64e0fbea734b855498f25d0753
http://blog.vmsplice.net/2015/08/virtio-vsock-zero-configuration.html
Thanks
Laszlo
next prev parent reply other threads:[~2015-09-03 23:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 9:16 [Qemu-devel] "Using Python to investigate EFI and ACPI" Laszlo Ersek
2015-09-03 9:41 ` Laszlo Ersek
2015-09-03 14:48 ` Jake Edge
2015-09-03 14:50 ` Josh Triplett
2015-09-03 15:22 ` josh
2015-09-03 15:53 ` Laszlo Ersek
2015-09-03 15:57 ` Moore, Robert
2015-09-03 16:16 ` Laszlo Ersek
2015-09-03 16:19 ` Moore, Robert
2015-09-03 16:41 ` josh
2015-09-03 17:19 ` Laszlo Ersek
2015-09-03 21:25 ` josh
2015-09-03 23:21 ` Laszlo Ersek [this message]
2015-09-04 17:11 ` josh
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=55E8D615.5070808@redhat.com \
--to=lersek@redhat.com \
--cc=edk2-devel@ml01.01.org \
--cc=imammedo@redhat.com \
--cc=jake@lwn.net \
--cc=jonathan.d.smith@intel.com \
--cc=josh@joshtriplett.org \
--cc=marcel@redhat.com \
--cc=markmb@redhat.com \
--cc=mtsirkin@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=robert.moore@intel.com \
--cc=somlo@cmu.edu \
--cc=zhaoshenglong@huawei.com \
/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).