lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 16 Dec 2011 15:40:01 +0800 From: Zang Hongyong <zanghongyong@...wei.com> To: Sasha Levin <levinsasha928@...il.com> Cc: linux-kernel@...r.kernel.org, mst@...hat.com, kvm@...r.kernel.org, virtualization@...ts.linux-foundation.org, netdev@...r.kernel.org, xiaowei.yang@...wei.com, hanweidong@...wei.com, wusongwei@...wei.com Subject: Re: [PATCH 0/2] vhot-net: Use kvm_memslots instead of vhost_memory to translate GPA to HVA 于 2011/12/16,星期五 15:05, Sasha Levin 写道: > On Fri, 2011-12-16 at 13:32 +0800, zanghongyong@...wei.com wrote: >> From: Hongyong Zang<zanghongyong@...wei.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? > But vhost-net is only used in virtualization situation. vhost_memory is maintained by user space qemu. In this way, the memory relationship can be accquired from kernel without the need of maintainence of vhost_memory from qemu. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists