From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: Rusty Russell <rusty@rustcorp.com.au>, kvm-devel <kvm@vger.kernel.org>
Subject: Re: splice() based interguest networking
Date: Tue, 02 Dec 2008 14:18:02 +0200 [thread overview]
Message-ID: <4935277A.9000206@redhat.com> (raw)
In-Reply-To: <49343BF9.30308@us.ibm.com>
Anthony Liguori wrote:
>
> 1) On TX, we vmsplice() from the sg buffer to one pipe. This will end
> up being vmsplice_to_pipe() in the kernel which is zero-copy.
>
That implies we do the MAC address switching in userspace (or that this
is a point-to-point protocol, which severely limits its usefulness).
I think we can still have one-copy interguest networking if we have
proper skb destructors; and since we need that for the more important
guest->external copyless support, we basically get it for free (if delayed).
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2008-12-02 12:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-01 19:33 splice() based interguest networking Anthony Liguori
2008-12-02 12:18 ` Avi Kivity [this message]
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=4935277A.9000206@redhat.com \
--to=avi@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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.