From: Anthony Liguori <anthony@codemonkey.ws>
To: Markus Armbruster <armbru@redhat.com>
Cc: "Blue Swirl" <blauwirbel@gmail.com>,
"Michael Roth" <mdroth@linux.vnet.ibm.com>,
qemu-devel@nongnu.org, "Zhi Yong Wu" <zwu.kernel@gmail.com>,
amit.shah@redhat.com, "Cam Macdonell" <cam@cs.ualberta.ca>,
"Lluís Vilanova" <vilanova@ac.upc.edu>
Subject: Re: [Qemu-devel] Insane virtio-serial semantics
Date: Thu, 08 Dec 2011 08:37:38 -0600 [thread overview]
Message-ID: <4EE0CBB2.8010402@codemonkey.ws> (raw)
In-Reply-To: <m31usf9xub.fsf@blackfin.pond.sub.org>
On 12/08/2011 04:11 AM, Markus Armbruster wrote:
> Anthony Liguori<anthony@codemonkey.ws> writes:
>> And yes, I can't help but think of Dave Millers comments long ago that
>> any PV transport is eventually going to reinvent TCP, poorly.
>
> No doubt then, no doubt now. But if I remember correctly, we didn't
> create virtio-serial because we thought we could do better than TCP/IP.
> We thought we need a zero-config communication channel that doesn't
> interfere in any way with the guest's networking. Since the network
> folks were unwilling to give us one ("use TCP already"), we looked for
> another bare metal thing to imitate, and chose serial lines.
>
> Now, comparing serial lines to TCP/IP makes no sense. Different layers.
virtio-serial is not a serial line. It attempts to have connection semantics
(like a socket) which is what the fundamental problem is.
It probably makes sense to have a virtio-serial2 that is exposed to the guest as
a tty device and stick strictly to serial semantics.
> Layering a real network protocol on top of serial line is possible; SLIP
> exists. But as long as we insist on "don't interfere in any way with
> the guest's networking", we can't use TCP, and thus are doomed to
> reinvent it, poorly.
I think we just got too clever.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2011-12-08 14:37 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-05 22:22 [Qemu-devel] [PATCH v2 0/5] backdoor: lightweight guest-to-QEMU backdoor channel Lluís Vilanova
2011-12-05 22:22 ` [Qemu-devel] [PATCH v2 1/5] backdoor: Add documentation Lluís Vilanova
2011-12-06 22:36 ` Peter Maydell
2011-12-06 22:51 ` Anthony Liguori
2011-12-06 22:50 ` Anthony Liguori
2011-12-05 22:22 ` [Qemu-devel] [PATCH v2 2/5] backdoor: Add build infrastructure Lluís Vilanova
2011-12-05 22:22 ` [Qemu-devel] [PATCH v2 3/5] backdoor: [*-user] Add QEMU-side proxy to "libbackdoor.a" Lluís Vilanova
2011-12-05 22:23 ` [Qemu-devel] [PATCH v2 4/5] backdoor: [softmmu] " Lluís Vilanova
2011-12-06 19:55 ` Anthony Liguori
2011-12-06 22:30 ` Lluís Vilanova
2011-12-06 22:35 ` Anthony Liguori
2011-12-06 22:37 ` Peter Maydell
2011-12-07 8:21 ` [Qemu-devel] Insane virtio-serial semantics (was: [PATCH v2 4/5] backdoor: [softmmu] Add QEMU-side proxy to "libbackdoor.a") Markus Armbruster
2011-12-07 13:49 ` [Qemu-devel] Insane virtio-serial semantics Anthony Liguori
2011-12-07 19:44 ` Michael Roth
2011-12-07 19:53 ` Anthony Liguori
2011-12-08 10:11 ` Markus Armbruster
2011-12-08 14:37 ` Anthony Liguori [this message]
2011-12-06 22:39 ` [Qemu-devel] [PATCH v2 4/5] backdoor: [softmmu] Add QEMU-side proxy to "libbackdoor.a" Lluís Vilanova
2011-12-05 22:23 ` [Qemu-devel] [PATCH v2 5/5] backdoor: Add guest-side library Lluís Vilanova
2011-12-06 22:52 ` [Qemu-devel] [PATCH v2 0/5] backdoor: lightweight guest-to-QEMU backdoor channel Anthony Liguori
2011-12-07 12:21 ` Lluís Vilanova
2011-12-07 13:55 ` Anthony Liguori
2011-12-07 15:23 ` Lluís Vilanova
2011-12-07 15:48 ` Anthony Liguori
2011-12-07 16:59 ` Lluís Vilanova
2011-12-07 17:48 ` Anthony Liguori
2011-12-07 18:35 ` Lluís Vilanova
2011-12-07 18:51 ` Peter Maydell
2011-12-07 18:54 ` Anthony Liguori
2011-12-07 20:13 ` Lluís Vilanova
2011-12-07 22:03 ` Lluís Vilanova
2011-12-08 20:45 ` Blue Swirl
2011-12-08 14:05 ` Stefan Hajnoczi
2011-12-08 18:57 ` Lluís Vilanova
2011-12-08 20:57 ` Blue Swirl
2011-12-08 22:16 ` Lluís Vilanova
2011-12-09 11:23 ` Stefan Hajnoczi
2011-12-09 20:55 ` Lluís Vilanova
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=4EE0CBB2.8010402@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=amit.shah@redhat.com \
--cc=armbru@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=cam@cs.ualberta.ca \
--cc=mdroth@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=vilanova@ac.upc.edu \
--cc=zwu.kernel@gmail.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).