| 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: <20110728144740.GA26744@infradead.org> Date: Thu, 28 Jul 2011 10:47:40 -0400 From: Christoph Hellwig <hch@...radead.org> To: Liu Yuan <namei.unix@...il.com> Cc: "Michael S. Tsirkin" <mst@...hat.com>, Rusty Russell <rusty@...tcorp.com.au>, Avi Kivity <avi@...hat.com>, kvm@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [RFC PATCH] vhost-blk: An in-kernel accelerator for virtio-blk On Thu, Jul 28, 2011 at 10:29:05PM +0800, Liu Yuan wrote: > From: Liu Yuan <tailai.ly@...bao.com> > > Vhost-blk driver is an in-kernel accelerator, intercepting the > IO requests from KVM virtio-capable guests. It is based on the > vhost infrastructure. > > This is supposed to be a module over latest kernel tree, but it > needs some symbols from fs/aio.c and fs/eventfd.c to compile with. > So currently, after applying the patch, you need to *recomplie* > the kernel. > > Usage: > $kernel-src: make M=drivers/vhost > $kernel-src: sudo insmod drivers/vhost/vhost_blk.ko > > After insmod, you'll see /dev/vhost-blk created. done! You'll need to send the changes for existing code separately. If you're going mostly for raw blockdevice access just calling submit_bio will shave even more overhead off, and simplify the code a lot. -- 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