All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] configure: add an option to disable vlans
Date: Tue, 08 Jun 2010 13:01:38 -0500	[thread overview]
Message-ID: <4C0E8582.9010903@codemonkey.ws> (raw)
In-Reply-To: <201006081537.22364.paul@codesourcery.com>

On 06/08/2010 09:37 AM, Paul Brook wrote:
>> I see three possible options to handle this.
>>
>>     (1) Write a hub (or morph the current vlan code into this).  Then
>>         you can do something like:
>>
>>               qemu -netdev socket,id=p1 \
>>                    -netdev user,id=p2   \
>>                    -netdev dump,id=p3 \
>>                    -switch peer=p1,peer=p2,monitor=p3,port=p4 \
>>                    -device $nic,netdev=p4
>>
>>     (2) Implement the same as external daemon which can be combined with
>>         -netdev socket.
>>
>>     (3) Just point people who need this to the various virtual switch
>>         projects (vde, ...) they can use and drop vlan.
>>      
> (2) is just a special case of (3), where we decide that the existing
> implementations suck and go write our own.
>    

To the extent that (1) is valuable, I think it's the best approach.  I'd 
vote for officially deprecating vlans for 0.13 and then seeing how much 
people complain.  If no one complains too much, then let's not bother 
introducing -switch.

Regards,

Anthony Liguori

> Paul
>    

  reply	other threads:[~2010-06-08 18:01 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-07 15:03 [Qemu-devel] [PATCH] configure: add an option to disable vlans Michael S. Tsirkin
2010-06-07 16:16 ` Paul Brook
2010-06-07 16:17   ` Michael S. Tsirkin
2010-06-07 16:42     ` Paul Brook
2010-06-07 16:52       ` Anthony Liguori
2010-06-07 19:21         ` Michael S. Tsirkin
2010-06-07 20:40           ` Anthony Liguori
2010-06-07 20:58             ` Michael S. Tsirkin
2010-06-07 21:37               ` Anthony Liguori
2010-06-07 21:57                 ` Anthony Liguori
2010-06-08 12:13                   ` Michael S. Tsirkin
2010-06-08 13:03                     ` Anthony Liguori
2010-06-08 13:07                       ` Michael S. Tsirkin
2010-06-08 11:09             ` Michael S. Tsirkin
2010-06-08 13:02               ` Anthony Liguori
2010-06-08 13:14                 ` Michael S. Tsirkin
2010-06-08 14:25                 ` Gerd Hoffmann
2010-06-08 14:37                   ` Paul Brook
2010-06-08 18:01                     ` Anthony Liguori [this message]
2010-06-07 17:41       ` Michael S. Tsirkin
2010-06-09  7:44         ` Markus Armbruster
2010-06-10  7:20           ` Chris Webb
2010-06-10  8:43             ` Michael S. Tsirkin
2010-06-08 12:17   ` 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=4C0E8582.9010903@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=kraxel@redhat.com \
    --cc=mst@redhat.com \
    --cc=paul@codesourcery.com \
    --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.