From: Paolo Bonzini <pbonzini@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] RFC: Universal encryption on QEMU I/O channels
Date: Wed, 04 Feb 2015 16:22:26 +0100 [thread overview]
Message-ID: <54D23932.8060101@redhat.com> (raw)
In-Reply-To: <20150204151105.GY3032@redhat.com>
On 04/02/2015 16:11, Daniel P. Berrange wrote:
> > For GIO/GIOChannel, you'd have to choose between zerocopy and many
> > syscalls, or one copy and few syscalls. Since every page has two iov
> > entries, one of which is just 8 bytes, one copy and few syscalls is
> > probably faster---but still only half the speed of writev.
>
> That could be an argument in favour of defining a QEMUIOChannel
> instead. The use of GIOChannel is only compelling if we gain some
> significant benefit from using the standard glib API in this scenario
> and I'm not clear that we really do, other than developer familiarity
> with glib.
GIOChannel's advantage is that---even though it may not be used for
regular migration---integration with chardev would be really easy.
> GIO could be compelling if we could leverage its TLS integration
I agree.
Paolo
next prev parent reply other threads:[~2015-02-04 15:29 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-04 11:32 [Qemu-devel] RFC: Universal encryption on QEMU I/O channels Daniel P. Berrange
2015-02-04 12:43 ` Paolo Bonzini
2015-02-04 13:00 ` Daniel P. Berrange
2015-02-04 13:42 ` Paolo Bonzini
2015-02-04 14:08 ` Daniel P. Berrange
2015-02-04 14:23 ` Paolo Bonzini
2015-02-04 14:34 ` Daniel P. Berrange
2015-02-04 15:04 ` Paolo Bonzini
2015-02-04 15:11 ` Daniel P. Berrange
2015-02-04 15:22 ` Paolo Bonzini [this message]
2015-02-04 15:26 ` Daniel P. Berrange
2015-02-04 16:46 ` Paolo Bonzini
2015-02-05 14:38 ` Stefan Hajnoczi
2015-02-05 14:44 ` Cornelia Huck
2015-02-05 14:45 ` Peter Maydell
2015-02-04 13:49 ` Markus Armbruster
2015-02-04 13:55 ` Peter Maydell
2015-02-04 16:33 ` Markus Armbruster
2015-02-04 16:41 ` Daniel P. Berrange
2015-02-04 20:41 ` Peter Maydell
2015-02-04 21:06 ` Paolo Bonzini
2015-02-05 7:57 ` Markus Armbruster
2015-02-04 13:08 ` Dr. David Alan Gilbert
2015-02-04 14:02 ` Daniel P. Berrange
2015-02-04 14:28 ` Paolo Bonzini
2015-02-04 14:48 ` Marcel Apfelbaum
2015-02-04 14:50 ` Daniel P. Berrange
2015-02-04 18:34 ` Eric Blake
2015-02-05 9:11 ` Dr. David Alan Gilbert
2015-02-04 14:27 ` Paolo Bonzini
2015-02-04 14:37 ` Dr. David Alan Gilbert
2015-03-06 17:18 ` Daniel P. Berrange
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=54D23932.8060101@redhat.com \
--to=pbonzini@redhat.com \
--cc=berrange@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.