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: <4BA5F50B.8080302@redhat.com> Date: Sun, 21 Mar 2010 12:29:31 +0200 From: Avi Kivity <avi@...hat.com> To: "Michael S. Tsirkin" <mst@...hat.com> CC: Sridhar Samudrala <samudrala.sridhar@...il.com>, netdev <netdev@...r.kernel.org>, "kvm@...r.kernel.org" <kvm@...r.kernel.org>, gleb@...hat.com Subject: Re: Unable to create more than 1 guest virtio-net device using vhost-net backend On 03/21/2010 12:15 PM, Michael S. Tsirkin wrote: >>> Nothing easy that I can see. Each device needs 2 of these. Avi, Gleb, >>> any objections to increasing the limit to say 16? That would give us >>> 5 more devices to the limit of 6 per guest. >>> >>> >> Increase it to 200, then. >> > OK. I think we'll also need a smarter allocator > than bus->dev_count++ than we now have. Right? > No, why? Eventually we'll want faster scanning than the linear search we employ now, though. >> Is the limit visible to userspace? If not, we need to expose it. >> > I don't think it's visible: it seems to be used in a single > place in kvm. Let's add an ioctl? Note that qemu doesn't > need it now ... > We usually expose limits via KVM_CHECK_EXTENSION(KVM_CAP_BLAH). We can expose it via KVM_CAP_IOEVENTFD (and need to reserve iodev entries for those). -- error compiling committee.c: too many arguments to function -- 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