From: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: kvm@vger.kernel.org, jan.kiszka@siemens.com,
qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>,
zwu.kernel@gmail.com, wuzhy@linux.vnet.ibm.com,
Stefan Hajnoczi <stefanha@gmail.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3 00/16] net: hub-based networking
Date: Mon, 28 May 2012 12:17:04 +0100 [thread overview]
Message-ID: <20120528111704.GD30438@stefanha-thinkpad.localdomain> (raw)
In-Reply-To: <20120525105628.1a1f3f8d@doriath.home>
On Fri, May 25, 2012 at 10:56:28AM -0300, Luiz Capitulino wrote:
> On Fri, 25 May 2012 15:47:28 +0200
> Paolo Bonzini <pbonzini@redhat.com> wrote:
>
> > Il 25/05/2012 15:43, Luiz Capitulino ha scritto:
> > >> Yeah, VDE probably includes something like an hub. But then we could
> > >> drop even "-net socket", "-net udp", "-net dump", and only leave in
> > >> vde+tap+slirp. Or even move slirp into VDE. :) That's a very different
> > >> thing.
> > >
> > > Let's start with what is hurting us.
> >
> > But is it? The patch makes it quite clean.
>
> vlan is and the cleanest solution is to drop it.
For the sake of the argument, here's what we'd need:
1. Patches to remove vlan completely from QEMU.
2. net/dump.c alternative.
Packet capture could be done like this:
-netdev tap,dump=capture.pcap,...
You specify the "dump" option on a netdev giving a filename to use for
the pcap file. The net/dump.c would need to be called from net.c or
maybe net/queue.c.
What we need to decide is whether it's okay to drop QEMU "VLANs"
completely and change dump command-line syntax?
I think vlan-hub doesn't hurt anyone because the code has been isolated
and we keep backwards compatibility. So I'd personally still go the
vlan-hub route for QEMU 1.x.
Stefan
next prev parent reply other threads:[~2012-05-28 11:17 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-24 17:59 [Qemu-devel] [PATCH v3 00/16] net: hub-based networking zwu.kernel
2012-05-24 17:59 ` [Qemu-devel] [PATCH v3 01/16] net: Add a hub net client zwu.kernel
2012-05-24 17:59 ` [Qemu-devel] [PATCH v3 02/16] net: Use hubs for the vlan feature zwu.kernel
2012-05-24 17:59 ` [Qemu-devel] [PATCH v3 03/16] net: Look up 'vlan' net clients using hubs zwu.kernel
2012-05-24 17:59 ` [Qemu-devel] [PATCH v3 04/16] hub: Check that hubs are configured correctly zwu.kernel
2012-05-24 17:59 ` [Qemu-devel] [PATCH v3 05/16] net: Drop vlan argument to qemu_new_net_client() zwu.kernel
2012-05-24 17:59 ` [Qemu-devel] [PATCH v3 06/16] net: Remove vlan qdev property zwu.kernel
2012-05-24 17:59 ` [Qemu-devel] [PATCH v3 07/16] net: Remove vlan code from net.c zwu.kernel
2012-05-24 17:59 ` [Qemu-devel] [PATCH v3 08/16] net: Remove VLANState zwu.kernel
2012-05-24 17:59 ` [Qemu-devel] [PATCH v3 09/16] net: Rename non_vlan_clients to net_clients zwu.kernel
2012-05-24 17:59 ` [Qemu-devel] [PATCH v3 10/16] net: Rename VLANClientState to NetClientState zwu.kernel
2012-05-24 17:59 ` [Qemu-devel] [PATCH v3 11/16] net: Rename vc local variables to nc zwu.kernel
2012-05-24 17:59 ` [Qemu-devel] [PATCH v3 12/16] net: Rename qemu_del_vlan_client() to qemu_del_net_client() zwu.kernel
2012-05-24 17:59 ` [Qemu-devel] [PATCH v3 13/16] net: Make the monitor output more reasonable hub info zwu.kernel
2012-05-24 20:34 ` Jan Kiszka
2012-05-25 0:48 ` Zhi Yong Wu
2012-05-25 12:00 ` Zhi Yong Wu
2012-05-25 13:49 ` Jan Kiszka
2012-05-25 13:58 ` Zhi Yong Wu
2012-05-24 17:59 ` [Qemu-devel] [PATCH v3 14/16] net: cleanup deliver/deliver_iov func pointers zwu.kernel
2012-05-24 17:59 ` [Qemu-devel] [PATCH v3 15/16] net: determine if packets can be sent before net queue deliver packets zwu.kernel
2012-05-24 17:59 ` [Qemu-devel] [PATCH v3 16/16] hub: add the support for hub own flow control zwu.kernel
2012-05-25 7:04 ` Paolo Bonzini
2012-05-25 7:48 ` Zhi Yong Wu
2012-05-25 10:08 ` Paolo Bonzini
2012-05-25 10:54 ` Zhi Yong Wu
2012-05-25 8:04 ` Zhi Yong Wu
2012-05-25 8:18 ` Zhi Yong Wu
2012-05-24 20:53 ` [Qemu-devel] [PATCH v3 00/16] net: hub-based networking Luiz Capitulino
2012-05-25 0:47 ` Zhi Yong Wu
2012-05-25 12:49 ` Luiz Capitulino
2012-05-25 10:07 ` Stefan Hajnoczi
2012-05-25 11:18 ` Markus Armbruster
2012-05-25 12:01 ` Stefan Hajnoczi
2012-05-25 12:30 ` Markus Armbruster
2012-05-25 12:53 ` Luiz Capitulino
2012-05-25 12:59 ` Paolo Bonzini
2012-05-25 13:07 ` Luiz Capitulino
2012-05-25 13:14 ` Paolo Bonzini
2012-05-25 13:18 ` Luiz Capitulino
2012-05-25 13:19 ` Paolo Bonzini
2012-05-25 13:30 ` Luiz Capitulino
2012-05-25 13:37 ` Paolo Bonzini
2012-05-25 13:43 ` Luiz Capitulino
2012-05-25 13:47 ` Paolo Bonzini
2012-05-25 13:56 ` Luiz Capitulino
2012-05-28 11:17 ` Stefan Hajnoczi [this message]
2012-05-28 13:25 ` Luiz Capitulino
[not found] ` <m3ehq3tne0.fsf@blackfin.pond.sub.org>
2012-06-04 4:48 ` Anthony Liguori
2012-06-04 7:24 ` Markus Armbruster
2012-06-04 4:56 ` Anthony Liguori
2012-06-04 13:09 ` Luiz Capitulino
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=20120528111704.GD30438@stefanha-thinkpad.localdomain \
--to=stefanha@linux.vnet.ibm.com \
--cc=armbru@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=lcapitulino@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=wuzhy@linux.vnet.ibm.com \
--cc=zwu.kernel@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).