From: Jan Kiszka <jan.kiszka@siemens.com>
To: Zhi Yong Wu <zwu.kernel@gmail.com>
Cc: "stefanha@linux.vnet.ibm.com" <stefanha@linux.vnet.ibm.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linuxram@us.ibm.com" <linuxram@us.ibm.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"wuzhy@linux.vnet.ibm.com" <wuzhy@linux.vnet.ibm.com>,
"pbonzini@redhat.com" <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 13/15] net: Remove obsolete vlan info
Date: Thu, 24 May 2012 09:09:54 -0300 [thread overview]
Message-ID: <4FBE2512.50704@siemens.com> (raw)
In-Reply-To: <CAEH94LiUTPeSc1wtpRw--R_x4GRzS2N-jTXpLKZ1+WAyBTVsiQ@mail.gmail.com>
On 2012-05-23 23:42, Zhi Yong Wu wrote:
> On Wed, May 23, 2012 at 11:41 PM, Jan Kiszka <jan.kiszka@siemens.com> wrote:
>> On 2012-05-23 12:14, zwu.kernel@gmail.com wrote:
>>> From: Zhi Yong Wu <wuzhy@linux.vnet.ibm.com>
>>>
>>> Signed-off-by: Zhi Yong Wu <wuzhy@linux.vnet.ibm.com>
>>> ---
>>> net.c | 1 -
>>> 1 files changed, 0 insertions(+), 1 deletions(-)
>>>
>>> diff --git a/net.c b/net.c
>>> index 61dc28d..8c8e703 100644
>>> --- a/net.c
>>> +++ b/net.c
>>> @@ -1079,7 +1079,6 @@ void do_info_network(Monitor *mon)
>>> NetClientState *nc, *peer;
>>> net_client_type type;
>>>
>>> - monitor_printf(mon, "Devices not on any VLAN:\n");
>>> QTAILQ_FOREACH(nc, &net_clients, next) {
>>> peer = nc->peer;
>>> type = nc->info->type;
>>
>> This looks suspicious - or the patch description is improvable. This is
>> really just about removing that headline? And what about the indention
>> of the lines printed afterward?
> As you have known, vlan concept is replaced with hub. So i think that
> it is more reasonable to remove this in monitor.
That is true. But the output formatting is still improvable.
>>
>> It also leads me to the question how hub-based networks will be
>> visualized on "info network", specifically when there are multiple hubs.
>> Can you provide some more complex example of an info network output?
>
> (qemu) info network
> virtio-net-pci.0: type=nic,model=virtio-net-pci,macaddr=52:54:00:12:34:56
> \ hub0port0: type=(null),
> virtio-net-pci.1: type=nic,model=virtio-net-pci,macaddr=52:54:00:12:34:57
> \ hub1port0: type=(null),
> hub 1
> port 1 peer user.1
> port 0 peer virtio-net-pci.1
> hub 0
> port 1 peer user.0
> port 0 peer virtio-net-pci.0
What about a layout like this:
hub.0
\ virtio-net-pci.0: ...
\ virtio-net-pci.1: ...
\ user.0: ...
hub.1
\ e1000.0: ...
e1000.1: ...
\ user.1: ...
ie. printing the hubs first, listing all the peers of their ports
underneath them. Also, things like "type=(null)" should be avoided.
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2012-05-24 12:10 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 15:13 [Qemu-devel] [PATCH v2 00/15] net: hub-based networking zwu.kernel
2012-05-23 15:13 ` [Qemu-devel] [PATCH v2 01/15] net: Add a hub net client zwu.kernel
2012-05-23 15:13 ` [Qemu-devel] [PATCH v2 02/15] net: Use hubs for the vlan feature zwu.kernel
2012-05-23 15:13 ` [Qemu-devel] [PATCH v2 03/15] net: Look up 'vlan' net clients using hubs zwu.kernel
2012-05-23 15:13 ` [Qemu-devel] [PATCH v2 04/15] hub: Check that hubs are configured correctly zwu.kernel
2012-05-23 15:13 ` [Qemu-devel] [PATCH v2 05/15] net: Drop vlan argument to qemu_new_net_client() zwu.kernel
2012-05-23 15:13 ` [Qemu-devel] [PATCH v2 06/15] net: Remove vlan qdev property zwu.kernel
2012-05-23 15:13 ` [Qemu-devel] [PATCH v2 07/15] net: Remove vlan code from net.c zwu.kernel
2012-05-23 15:13 ` [Qemu-devel] [PATCH v2 08/15] net: Remove VLANState zwu.kernel
2012-05-23 15:13 ` [Qemu-devel] [PATCH v2 09/15] net: Rename non_vlan_clients to net_clients zwu.kernel
2012-05-23 15:14 ` [Qemu-devel] [PATCH v2 10/15] net: Rename VLANClientState to NetClientState zwu.kernel
2012-05-23 15:14 ` [Qemu-devel] [PATCH v2 11/15] net: Rename vc local variables to nc zwu.kernel
2012-05-23 15:14 ` [Qemu-devel] [PATCH v2 12/15] net: Rename qemu_del_vlan_client() to qemu_del_net_client() zwu.kernel
2012-05-23 15:14 ` [Qemu-devel] [PATCH v2 13/15] net: Remove obsolete vlan info zwu.kernel
2012-05-23 15:41 ` Jan Kiszka
2012-05-24 2:42 ` Zhi Yong Wu
2012-05-24 12:09 ` Jan Kiszka [this message]
2012-05-24 12:27 ` Zhi Yong Wu
2012-05-24 13:30 ` Jan Kiszka
2012-05-24 14:12 ` Zhi Yong Wu
2012-05-24 14:24 ` Jan Kiszka
2012-05-24 12:34 ` Zhi Yong Wu
2012-05-24 13:33 ` Jan Kiszka
2012-05-24 14:14 ` Zhi Yong Wu
2012-05-24 14:25 ` Jan Kiszka
2012-05-24 14:27 ` Zhi Yong Wu
2012-05-24 14:31 ` Jan Kiszka
2012-05-24 14:38 ` Zhi Yong Wu
2012-05-24 14:43 ` Jan Kiszka
2012-05-24 14:51 ` Zhi Yong Wu
2012-05-24 15:01 ` Jan Kiszka
2012-05-24 14:59 ` Zhi Yong Wu
2012-05-24 12:54 ` Zhi Yong Wu
2012-05-23 15:14 ` [Qemu-devel] [PATCH v2 14/15] net: cleanup deliver/deliver_iov func pointers zwu.kernel
2012-05-23 15:14 ` [Qemu-devel] [PATCH v2 15/15] net: invoke qemu_can_send_packet only before net queue sending function zwu.kernel
2012-05-23 16:00 ` Paolo Bonzini
2012-05-24 4:05 ` Zhi Yong Wu
2012-05-24 10:07 ` Paolo Bonzini
2012-05-24 11:58 ` Zhi Yong Wu
2012-05-24 12:02 ` Paolo Bonzini
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=4FBE2512.50704@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=linuxram@us.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.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).