From: Avi Kivity <avi@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Sridhar Samudrala <samudrala.sridhar@gmail.com>,
netdev <netdev@vger.kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
gleb@redhat.com
Subject: Re: Unable to create more than 1 guest virtio-net device using vhost-net backend
Date: Sun, 21 Mar 2010 12:29:31 +0200 [thread overview]
Message-ID: <4BA5F50B.8080302@redhat.com> (raw)
In-Reply-To: <20100321101527.GH6443@redhat.com>
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
next prev parent reply other threads:[~2010-03-21 10:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-19 22:19 Unable to create more than 1 guest virtio-net device using vhost-net backend Sridhar Samudrala
2010-03-21 9:55 ` Michael S. Tsirkin
2010-03-21 10:11 ` Avi Kivity
2010-03-21 10:15 ` Michael S. Tsirkin
2010-03-21 10:29 ` Avi Kivity [this message]
2010-03-21 11:34 ` Michael S. Tsirkin
2010-03-21 11:58 ` Avi Kivity
2010-03-22 18:16 ` Michael S. Tsirkin
2010-03-22 23:41 ` Sridhar Samudrala
2010-03-21 10:21 ` Gleb Natapov
2010-03-21 10:31 ` Avi Kivity
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4BA5F50B.8080302@redhat.com \
--to=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=samudrala.sridhar@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).