From: Shirley Ma <mashirle@us.ibm.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Arnd Bergmann <arnd@arndb.de>, Avi Kivity <avi@redhat.com>,
"Xin, Xiaohui" <xiaohui.xin@intel.com>,
David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 2/2] macvtap: TX zero copy between guest and host kernel
Date: Tue, 14 Sep 2010 10:02:25 -0700 [thread overview]
Message-ID: <1284483745.13351.71.camel@localhost.localdomain> (raw)
In-Reply-To: <20100914162952.GB13560@redhat.com>
On Tue, 2010-09-14 at 18:29 +0200, Michael S. Tsirkin wrote:
> Precisely. This is what the patch from Xin Xiaohui does. That code
> already seems to do most of what you are trying to do, right?
I thought host pins guest kernel buffer pages was good enough for TX
thought I didn't look up xiaohui's vhost asycn io patch in details.
What's the performance data Xiaohui got from using kiocb? I haven't seen
any performance number from him yet.
> The main thing missing seems to be macvtap integration, so that we can
> fall back
> on data copy if zero copy is unavailable?
> How hard would it be to basically link the mp and macvtap modules
> together to get us this functionality? Anyone?
The simple integration is using macvtap + xiaohui's vhost asycn io
patch. I can make a try for TX only.
Thanks
Shirley
next prev parent reply other threads:[~2010-09-14 17:02 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-13 20:43 [RFC PATCH 0/1] macvtap TX zero copy between guest and host kernel Shirley Ma
2010-09-13 20:47 ` RFC PATCH 1/2] macvtap: A new sock zero copy flag Shirley Ma
2010-09-13 20:48 ` [RFC PATCH 2/2] macvtap: TX zero copy between guest and host kernel Shirley Ma
2010-09-14 3:17 ` David Miller
2010-09-14 9:12 ` Avi Kivity
2010-09-14 15:05 ` Shirley Ma
2010-09-14 15:21 ` Arnd Bergmann
2010-09-14 15:22 ` Michael S. Tsirkin
2010-09-14 16:00 ` Shirley Ma
2010-09-14 16:29 ` Michael S. Tsirkin
2010-09-14 17:02 ` Shirley Ma [this message]
2010-09-14 18:27 ` Michael S. Tsirkin
2010-09-14 18:49 ` Shirley Ma
2010-09-14 19:01 ` Michael S. Tsirkin
2010-09-14 19:20 ` Shirley Ma
2010-09-15 5:31 ` Michael S. Tsirkin
2010-09-14 19:36 ` Shirley Ma
2010-09-15 5:12 ` Michael S. Tsirkin
2010-09-15 6:21 ` Shirley Ma
2010-09-15 10:10 ` Michael S. Tsirkin
2010-09-15 14:52 ` Shirley Ma
2010-09-15 15:04 ` Michael S. Tsirkin
2010-09-15 15:39 ` Michael S. Tsirkin
2010-09-15 17:00 ` Shirley Ma
2010-09-15 17:30 ` Michael S. Tsirkin
2010-09-15 18:48 ` Shirley Ma
2010-09-29 3:24 ` Shirley Ma
2010-09-29 8:16 ` Michael S. Tsirkin
2010-09-29 8:28 ` Michael S. Tsirkin
2010-09-29 14:33 ` Shirley Ma
2010-09-29 14:56 ` Shirley Ma
2010-09-29 14:31 ` Shirley Ma
2010-09-29 14:37 ` Shirley Ma
2010-09-29 15:14 ` Michael S. Tsirkin
2010-09-29 15:23 ` Shirley Ma
2010-09-15 2:46 ` Xin, Xiaohui
2010-09-15 9:58 ` Michael S. Tsirkin
2010-09-16 8:18 ` Xin, Xiaohui
2010-09-16 10:02 ` Michael S. Tsirkin
2010-09-15 1:56 ` Xin, Xiaohui
2010-09-15 1:50 ` Xin, Xiaohui
2010-09-15 2:40 ` Shirley Ma
2010-09-15 2:55 ` Xin, Xiaohui
2010-09-15 5:27 ` Michael S. Tsirkin
2010-09-15 6:17 ` Shirley Ma
2010-09-14 12:05 ` [RFC PATCH 0/1] macvtap " Michael S. Tsirkin
2010-09-14 15:15 ` Shirley Ma
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=1284483745.13351.71.camel@localhost.localdomain \
--to=mashirle@us.ibm.com \
--cc=arnd@arndb.de \
--cc=avi@redhat.com \
--cc=davem@davemloft.net \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=xiaohui.xin@intel.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).