From: Miguel Di Ciurcio Filho <miguel.filho@gmail.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Markus Armbruster <armbru@redhat.com>,
Luiz Capitulino <lcapitulino@redhat.com>,
qemu-devel@nongnu.org, avi@redhat.com
Subject: [Qemu-devel] Re: [PATCH 0/8] vlan cleanup
Date: Tue, 13 Jul 2010 09:22:03 -0300 [thread overview]
Message-ID: <AANLkTikSPDujyqCGQGp5gsomDS6SyIMOTcbaEUsGO23y@mail.gmail.com> (raw)
In-Reply-To: <4C3C04C4.8050804@web.de>
On Tue, Jul 13, 2010 at 3:16 AM, Jan Kiszka <jan.kiszka@web.de> wrote:
> Miguel Di Ciurcio Filho wrote:
>> This series removes the vlan stuff without mercy. I've tried to make the steps
>> as small as possible, but the last one is huge. I did some basic tests and
>> networking is still working, so reviews are welcome :-D
>
> Sorry, this is a bit too rude. This not only removes the vlan model,
> something one may talk about, but also the innocent socket back-ends and
> the useful pcap dump support.
>
> Socket back-ends allow quick and easy unprivileged inter-VM network
> setups. Nothing for production systems, but useful for testing purposes
> on boxes where taps are not allowed or unhandy to configure.
>
I agree that it might be handy sometimes, but one could use VDE for
that too. Runs on user-space and can be tunneled over SSH or netcat
[1].
Another option would be to make the socket backend properly work as a
netdev, so one could directly connect guest NICs on different hosts,
but on a 1:1 relationship.
> The dump client helps to debug user mode guest networks, namely slirp
> which you did not remove. If that should become the only use case for
> vlans with more than 2 nodes, we could think about making it a special
> feature of backend devices.
>
socket and dump are only used when the vlan backends are concerned, so
they don't have any useful meaning outside of that.
How about add dump hooks on backends? I don't think network backends
need to be stackable like block devices, thought.
> I'm open for cleanups here, but they do require a bit mercy - and should
> also mention the reason.
>
Well, basically there is a lot of "if (vlan) else if (peer)". While
discussing the query-netdev QMP command, no one has shown any love
about the vlan stuff at all, quite the contrary and it was kept out of
the protocol.
Regards,
Miguel
[1] http://wiki.virtualsquare.org/index.php/VDE#vde_plug
next prev parent reply other threads:[~2010-07-13 12:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-12 19:20 [Qemu-devel] [PATCH 0/8] vlan cleanup Miguel Di Ciurcio Filho
2010-07-12 19:20 ` [Qemu-devel] [PATCH 1/8] vlan cleanup: update documentation Miguel Di Ciurcio Filho
2010-07-14 6:11 ` Markus Armbruster
2010-07-12 19:20 ` [Qemu-devel] [PATCH 2/8] vlan cleanup: update options Miguel Di Ciurcio Filho
2010-07-14 6:20 ` Markus Armbruster
2010-07-12 19:20 ` [Qemu-devel] [PATCH 3/8] vlan cleanup: do not depend on socket and dump Miguel Di Ciurcio Filho
2010-07-12 19:20 ` [Qemu-devel] [PATCH 4/8] vlan cleanup: do not build " Miguel Di Ciurcio Filho
2010-07-12 19:20 ` [Qemu-devel] [PATCH 5/8] vlan cleanup: remove socket.h and socket.c Miguel Di Ciurcio Filho
2010-07-12 19:20 ` [Qemu-devel] [PATCH 6/8] vlan cleanup: remove dump.h and dump.c Miguel Di Ciurcio Filho
2010-07-12 19:20 ` [Qemu-devel] [PATCH 7/8] vlan cleanup: remove legacy monitor commands Miguel Di Ciurcio Filho
2010-07-12 19:20 ` [Qemu-devel] [PATCH 8/8] vlan cleanup: remove usage of VLANState Miguel Di Ciurcio Filho
2010-07-14 6:54 ` Markus Armbruster
2010-07-14 7:18 ` [Qemu-devel] " Jan Kiszka
2010-07-13 6:16 ` [Qemu-devel] Re: [PATCH 0/8] vlan cleanup Jan Kiszka
2010-07-13 12:22 ` Miguel Di Ciurcio Filho [this message]
2010-07-13 12:48 ` Jan Kiszka
2010-07-13 18:51 ` Anthony Liguori
2010-07-13 19:08 ` Jan Kiszka
2010-07-13 19:22 ` Anthony Liguori
2010-07-13 20:12 ` Jan Kiszka
2010-07-14 7:08 ` Markus Armbruster
2010-07-14 7:28 ` Jan Kiszka
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=AANLkTikSPDujyqCGQGp5gsomDS6SyIMOTcbaEUsGO23y@mail.gmail.com \
--to=miguel.filho@gmail.com \
--cc=armbru@redhat.com \
--cc=avi@redhat.com \
--cc=jan.kiszka@web.de \
--cc=lcapitulino@redhat.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 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).