All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Mark McLoughlin <markmc@redhat.com>
Cc: Michael Tokarev <mjt@tls.msk.ru>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	KVM list <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] net packet storms with multiple NICs
Date: Tue, 10 Nov 2009 19:38:48 -0600	[thread overview]
Message-ID: <4AFA15A8.4070402@codemonkey.ws> (raw)
In-Reply-To: <1256316218.31881.85.camel@blaa>

Mark McLoughlin wrote:
> On Fri, 2009-10-23 at 20:25 +0400, Michael Tokarev wrote:
>   
>> I've two questions:
>>
>> o what's the intended usage of all-vlan-equal case, when kvm (or qemu)
>>    reflects packets from one interface to another?  It's what bridge
>>    in linux is for, I think.
>>     
>
> I don't think it's necessarily an intended use-case for the vlan feature
>
>   
>> o why different -net guest -net host pairs are not getting different
>>    vlan= indexes by default, to stop the above-mentioned packet
>>    storms right away?  I think it's a wise default to assign different
>>    pairs to different vlans, by counting -net host and -net guest
>>    sequences.
>>     
>
> With 0.12, we're going to be de-emphasising the vlan feature and instead
> have NICs directly connected to host backends. The vlan feature will be
> just another host backend, but optional
>
> You'll start guests with e.g.:
>
>   -netdev tap,id=tap.0 -device virtio-net-pci,netdev=tap.0
>   

Which is not necessarily more friendly to a user, but it lays the 
foundation to be able to do a config file which in turns could be easily 
generated from a nic GUI/command line tool.

Regards,

Anthony Liguori

  parent reply	other threads:[~2009-11-11  1:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-23 16:25 net packet storms with multiple NICs Michael Tokarev
2009-10-23 16:25 ` [Qemu-devel] " Michael Tokarev
2009-10-23 16:33 ` Andreas Plesner Jacobsen
2009-10-23 16:33   ` [Qemu-devel] " Andreas Plesner Jacobsen
2009-10-23 16:57   ` Michael Tokarev
2009-10-23 16:57     ` [Qemu-devel] " Michael Tokarev
2009-10-23 16:43 ` [Qemu-devel] " Mark McLoughlin
2009-10-25 14:22   ` Avi Kivity
2009-10-26 13:40     ` Krumme, Chris
2009-10-26 13:40       ` Krumme, Chris
2009-10-26 13:44       ` Avi Kivity
2009-11-11  1:38   ` Anthony Liguori [this message]
2009-11-11  1:19 ` Paul Brook
2009-11-11  9:23   ` Michael Tokarev

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=4AFA15A8.4070402@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=kvm@vger.kernel.org \
    --cc=markmc@redhat.com \
    --cc=mjt@tls.msk.ru \
    --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.