public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: linux_kvm@proinbox.com
To: "Anthony Liguori" <anthony@codemonkey.ws>
Subject: Re: 8 NIC limit - patch - places limit at 32
Date: Wed, 06 Oct 2010 13:11:52 -0400	[thread overview]
Message-ID: <1286385112.6026.1398703073@webmail.messagingengine.com> (raw)
In-Reply-To: <4CAC719E.6060004@codemonkey.ws>

It's 8 otherwise- and after the patch is applied, it still only goes to
28 for some reason.
28's acceptable for my needs, so I'll step aside from here & leave it to
the experts.

As for the new -device method, that's all fine & good but AFAIK it's not
implemented on my platform, so this was the answer.

On Wed, 06 Oct 2010 07:54 -0500, "Anthony Liguori"
<anthony@codemonkey.ws> wrote:
> On 10/06/2010 12:46 AM, linux_kvm@proinbox.com wrote:
> > Attached is a patch that allows qemu to have up to 32 NICs, without
> > using the qdev -device method.
> >    
> 
> I'd rather there be no fixed limit and we validate that when add fails 
> because there isn't a TCP slot available, we do the right thing.
> 
> BTW, using -device, it should be possible to add a very high number of 
> nics because you can specify the PCI address including a function.  If 
> this doesn't Just Work today, we should make it work.
> 
> Regards,
> 
> Anthony Liguori
> 

  parent reply	other threads:[~2010-10-06 17:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-05 14:48 8 NIC limit linux_kvm
2010-10-05 15:24 ` Dustin Kirkland
     [not found]   ` <1286294888.11462.1398488135@webmail.messagingengine.com>
     [not found]     ` <1286295603.7731.28.camel@x200>
2010-10-06  5:46       ` 8 NIC limit - patch - places limit at 32 linux_kvm
     [not found]         ` <4CAC719E.6060004@codemonkey.ws>
2010-10-06 17:11           ` linux_kvm [this message]
2010-10-07  1:39             ` Chris Wright
2010-10-05 15:57 ` 8 NIC limit Markus Armbruster
2010-10-05 16:20   ` linux_kvm
2010-10-05 16:43 ` Brian Jackson

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=1286385112.6026.1398703073@webmail.messagingengine.com \
    --to=linux_kvm@proinbox.com \
    --cc=anthony@codemonkey.ws \
    /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