From: "Zhang Haoyu" <zhanghy@sangfor.com>
To: "Venkateswara Rao Nandigam" <venkateswararao.nandigam@citrix.com>,
"Marcus White" <roastedseaweed.k@gmail.com>
Cc: kvm <kvm@vger.kernel.org>
Subject: Re: RE: Some more basic questions..
Date: Tue, 3 Jun 2014 19:00:15 +0800 [thread overview]
Message-ID: <201406031900135822695@sangfor.com> (raw)
In-Reply-To: CALAJOd03U9mRkD0zA9-cfE7dP0v=1b9uE+k7-+KwaHDMW_CGow@mail.gmail.com
>>A few additional questions:)
>>
>>1. If IO to a block device goes through QEMU and not vhost, are there
>>data copies between kernel and user mode if I do IO to a block device
>>or is it zero copy? Kind of related to Question (2) also.
>>
>An additional copy will be avoided only by using vhost, so if you are using vhost you can call it zero copy realtively.
I know that kvm support network tx zero-copy when using vhost, but rx copy is still performed in vhost, because the NIC cannot determine
DMA to which VM's rx buffers before L2 switching(unless vhost using page-flip between HVA->HPA and GPA->HPA, or macvtap over SRIOV-VF is used).
Storage has no this limitation, can vhost-blk and vhost-scsi avoid data copy in both write and read?
IIUC, even if vhost is not used, qemu using linux native aio can avoid data copy between user and kernel space, right?
next prev parent reply other threads:[~2014-06-03 11:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-28 20:59 Some more basic questions Marcus White
2014-05-29 6:04 ` Venkateswara Rao Nandigam
2014-05-29 6:45 ` Zhang Haoyu
2014-05-30 4:06 ` Marcus White
2014-05-30 6:48 ` Zhang Haoyu
2014-06-02 21:19 ` Marcus White
2014-06-03 3:43 ` Zhang Haoyu
2014-06-03 4:53 ` Marcus White
2014-06-03 6:47 ` Zhang Haoyu
2014-06-03 6:54 ` Venkateswara Rao Nandigam
2014-06-03 11:00 ` Zhang Haoyu [this message]
2014-06-03 11:25 ` Venkateswara Rao Nandigam
2014-06-04 1:08 ` Marcus White
2014-06-05 4:42 ` Marcus White
2014-06-12 18:48 ` Marcus White
2014-06-03 12:51 ` Zhang Haoyu
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=201406031900135822695@sangfor.com \
--to=zhanghy@sangfor.com \
--cc=kvm@vger.kernel.org \
--cc=roastedseaweed.k@gmail.com \
--cc=venkateswararao.nandigam@citrix.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