From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1N23zs-00037j-4y
	for qemu-devel@nongnu.org; Sun, 25 Oct 2009 10:23:04 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1N23zn-000361-JX
	for qemu-devel@nongnu.org; Sun, 25 Oct 2009 10:23:03 -0400
Received: from [199.232.76.173] (port=45154 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1N23zn-00035u-CN
	for qemu-devel@nongnu.org; Sun, 25 Oct 2009 10:22:59 -0400
Received: from mx1.redhat.com ([209.132.183.28]:44938)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <avi@redhat.com>) id 1N23zm-0002Np-Rj
	for qemu-devel@nongnu.org; Sun, 25 Oct 2009 10:22:59 -0400
Message-ID: <4AE45F3E.5090208@redhat.com>
Date: Sun, 25 Oct 2009 16:22:54 +0200
From: Avi Kivity <avi@redhat.com>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] net packet storms with multiple NICs
References: <4AE1D903.5030709@msgid.tls.msk.ru>
	<1256316218.31881.85.camel@blaa>
In-Reply-To: <1256316218.31881.85.camel@blaa>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
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>

On 10/23/2009 06:43 PM, 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
>    

Well, it is.  vlan=x really means "the ethernet segment named x".  If 
you connect all your guest nics to one vlan, you are connecting them all 
to one ethernet segment, so any packet transmitted on one will be 
reflected on others.

Whether this is a useful feature is another matter, but the code is 
functioning as expected.

-- 
error compiling committee.c: too many arguments to function