From: Anthony Liguori <anthony@codemonkey.ws>
To: Avi Kivity <avi@redhat.com>
Cc: Anjali Kulkarni <anjali@juniper.net>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Hitting 29 NIC limit
Date: Thu, 14 Oct 2010 09:11:10 -0500 [thread overview]
Message-ID: <4CB70F7E.30308@codemonkey.ws> (raw)
In-Reply-To: <4CB7044A.4050705@redhat.com>
On 10/14/2010 08:23 AM, Avi Kivity wrote:
> On 10/14/2010 02:54 PM, Anthony Liguori wrote:
>>>> The key is to make the virtio-net devices multifunction and to fill
>>>> out all 8 functions for each slot.
>>>
>>> This is unlikely to work right wrt pci hotplug.
>>
>>
>> Yes. Our hotplug design is based on devices.. This is wrong, it
>> should be based on bus-level concepts (like PCI slots).
>>
>>> If we want to support a large number of interfaces, we need true
>>> multiport cards.
>>
>> This magic here creates a multiport virtio-net card so I'm not really
>> sure what you're suggesting. It would certainly be nice to make this
>> all more user friendly (and make hotplug work).
>>
>
> The big issue is to fix hotplug.
Yes, but this is entirely independent of multifunction devices.
Today we shoe-horn hot remove into device_del. Instead, we should have
explicit bus-level interfaces for hot remove.
Regards,
Anthony Liguori
> I don't see how we can make it user friendly, without making the
> ordinary case even more unfriendly. Looks like we need yet another
> level of indirection here.
>
next prev parent reply other threads:[~2010-10-14 14:11 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <C8DB7E5F.2FEA4%anjali@juniper.net>
2010-10-13 22:32 ` Hitting 29 NIC limit Anjali Kulkarni
2010-10-13 22:54 ` [Qemu-devel] " Anthony Liguori
2010-10-14 12:07 ` Avi Kivity
2010-10-14 12:10 ` Daniel P. Berrange
2010-10-14 12:57 ` Anthony Liguori
2010-10-18 20:07 ` H. Peter Anvin
2010-10-14 21:42 ` Richard W.M. Jones
2010-10-14 21:57 ` Anthony Liguori
2010-10-14 22:00 ` Anjali Kulkarni
2010-10-14 22:09 ` Anthony Liguori
2010-10-14 22:12 ` Anjali Kulkarni
2010-10-14 22:17 ` Anthony Liguori
2010-11-16 17:23 ` Michael S. Tsirkin
2010-11-16 19:00 ` Anthony Liguori
2010-10-14 22:08 ` [Qemu-devel] " Richard W.M. Jones
2010-10-14 12:36 ` Markus Armbruster
2010-10-14 12:59 ` Anthony Liguori
2010-10-15 9:11 ` Markus Armbruster
2010-10-15 18:49 ` Passing in additional info to guest OS and e1000 test suite? Anjali Kulkarni
2010-10-15 20:02 ` Anthony Liguori
2010-10-14 12:54 ` [Qemu-devel] Hitting 29 NIC limit Anthony Liguori
2010-10-14 13:23 ` Avi Kivity
2010-10-14 14:11 ` Anthony Liguori [this message]
2010-10-14 14:53 ` Avi Kivity
2010-10-28 20:52 ` [Qemu-devel] Hitting 29 NIC limit (+Intel VT-c) linux_kvm
2010-11-16 17:21 ` Hitting 29 NIC limit Michael S. Tsirkin
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=4CB70F7E.30308@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=anjali@juniper.net \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.