| 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: Thu, 21 Jan 2016 15:39:26 +0200 From: "Michael S. Tsirkin" <mst@...hat.com> To: virtio@...ts.oasis-open.org Cc: virtio-dev@...ts.oasis-open.org, kvm@...r.kernel.org, qemu-devel@...gnu.org, dev@...k.org, virtualization@...ts.linux-foundation.org, "Xie, Huawei" <huawei.xie@...el.com>, linux-kernel@...r.kernel.org Subject: virtio ring layout changes for optimal single-stream performance Hi all! I have been experimenting with alternative virtio ring layouts, in order to speed up single stream performance. I have just posted a benchmark I wrote for the purpose, and a (partial) alternative layout implementation. This achieves 20-40% reduction in virtio overhead in the (default) polling mode. http://article.gmane.org/gmane.linux.kernel.virtualization/26889 The layout is trying to be as simple as possible, to reduce the number of cache lines bouncing between CPUs. For benchmarking, the idea is to emulate virtio in user-space, artificially adding overhead for e.g. signalling to match what happens in case of a VM. I'd be very curious to get feedback on this, in particular, some people discussed using vectored operations to format virtio ring - would it conflict with this work? You are all welcome to post enhancements or more layout alternatives as patches. TODO: - documentation+discussion of interaction with CPU caching - thorough benchmarking of different configurations/hosts - experiment with event index replacements - better emulate vmexit/vmentry cost overhead - virtio spec proposal Thanks! -- MST
Powered by blists - more mailing lists