| 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
| ||
|
Message-ID: <4A83167E.2080701@codemonkey.ws> Date: Wed, 12 Aug 2009 14:22:38 -0500 From: Anthony Liguori <anthony@...emonkey.ws> To: "Michael S. Tsirkin" <mst@...hat.com> CC: Arnd Bergmann <arnd@...db.de>, virtualization@...ts.linux-foundation.org, "Ira W. Snyder" <iws@...o.caltech.edu>, netdev@...r.kernel.org, kvm@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH 2/2] vhost_net: a kernel-level virtio server Michael S. Tsirkin wrote: >> >> We discussed this before, and I still think this could be directly derived >> from struct virtqueue, in the same way that vring_virtqueue is derived from >> struct virtqueue. >> > > I prefer keeping it simple. Much of abstraction in virtio is due to the > fact that it needs to work on top of different hardware emulations: > lguest,kvm, possibly others in the future. vhost is always working on > real hardware, using eventfd as the interface, so it does not need that. > Actually, vhost may not always be limited to real hardware. We may on day use vhost as the basis of a driver domain. There's quite a lot of interest in this for networking. At any rate, I'd like to see performance results before we consider trying to reuse virtio code. Regards, Anthony Liguori -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists