From: Sasha Levin <levinsasha928@gmail.com>
To: zanghongyong@huawei.com
Cc: wusongwei@huawei.com, kvm@vger.kernel.org, mst@redhat.com,
netdev@vger.kernel.org, hanweidong@huawei.com,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
xiaowei.yang@huawei.com
Subject: Re: [PATCH 0/2] vhot-net: Use kvm_memslots instead of vhost_memory to translate GPA to HVA
Date: Fri, 16 Dec 2011 09:05:51 +0200 [thread overview]
Message-ID: <1324019151.4496.9.camel@lappy> (raw)
In-Reply-To: <1324013528-3663-1-git-send-email-zanghongyong@huawei.com>
On Fri, 2011-12-16 at 13:32 +0800, zanghongyong@huawei.com wrote:
> From: Hongyong Zang <zanghongyong@huawei.com>
>
> Vhost-net uses its own vhost_memory, which results from user space (qemu) info,
> to translate GPA to HVA. Since kernel's kvm structure already maintains the
> address relationship in its member *kvm_memslots*, these patches use kernel's
> kvm_memslots directly without the need of initialization and maintenance of
> vhost_memory.
Conceptually, vhost isn't aware of KVM - it's just a driver which moves
data from vq to a tap device and back. You can't simply add KVM specific
code into vhost.
Whats the performance benefit?
--
Sasha.
next prev parent reply other threads:[~2011-12-16 7:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-16 5:32 [PATCH 0/2] vhot-net: Use kvm_memslots instead of vhost_memory to translate GPA to HVA zanghongyong
2011-12-16 5:32 ` [PATCH 1/2] kvm: Introduce get_kvm_from_task zanghongyong
2011-12-16 5:32 ` [PATCH 2/2] vhost-net: Use kvm_memslots for address translation zanghongyong
2011-12-16 7:05 ` [PATCH 0/2] vhot-net: Use kvm_memslots instead of vhost_memory to translate GPA to HVA Takuya Yoshikawa
2011-12-16 7:05 ` Sasha Levin [this message]
2011-12-16 7:40 ` Zang Hongyong
2011-12-16 7:59 ` Sasha Levin
2011-12-16 8:07 ` Sasha Levin
2011-12-16 8:18 ` Zang Hongyong
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=1324019151.4496.9.camel@lappy \
--to=levinsasha928@gmail.com \
--cc=hanweidong@huawei.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=wusongwei@huawei.com \
--cc=xiaowei.yang@huawei.com \
--cc=zanghongyong@huawei.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).