From: Zaboj Campula <zaboj.campula@post•cz>
To: Jiri Benc <jbenc@redhat•com>
Cc: Jiri Pirko <jiri@resnulli•us>, netdev@vger•kernel.org
Subject: Re: [PATCH] iproute2: show network device dependency tree
Date: Thu, 02 Mar 2017 19:51:28 +0000 [thread overview]
Message-ID: <1488484288.5717.1.camel@post.cz> (raw)
In-Reply-To: <20170301112228.713bd4d5@griffin>
On Wed, 2017-03-01 at 11:22 +0100, Jiri Benc wrote:
> On Tue, 28 Feb 2017 20:07:37 +0000, Zaboj Campula wrote:
> > Well it is impossible to draw a simple tree showing the configuration
> > exactly with all details. May be it is too ambitious to draw a tree
> > at all.
>
> I tried that and failed. I didn't want to have something that would
> work only "somehow" as that would create confusion instead of helping.
OK, I give up. My patch was naive and I deleted it.
Nevertheless I still think it would be useful to show network
interfaces dependencies in a pure text format.
> Consider the very simple case of an interface with two vlan interfaces
> and both of them in a bridge.
>
> vlan0
> / \
> eth0 br0
> \ /
> vlan1
>
> You can't represent this in a tree view. And this is just a very simple
> example, in reality it tends to be much more complex.
Perhaps something like that:
eth0
vlan0
br0
vlan1
br0
next prev parent reply other threads:[~2017-03-02 20:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-25 16:59 [PATCH] iproute2: show network device dependency tree Zaboj Campula
2017-02-25 17:39 ` Jiri Pirko
2017-02-25 20:22 ` Zaboj Campula
2017-02-26 7:56 ` Jiri Pirko
2017-02-26 14:00 ` Zaboj Campula
2017-02-26 14:46 ` Jiri Pirko
2017-02-27 16:38 ` Jiri Benc
2017-02-28 20:07 ` Zaboj Campula
2017-03-01 10:22 ` Jiri Benc
2017-03-02 19:51 ` Zaboj Campula [this message]
2017-02-27 17:26 ` Stephen Hemminger
2017-02-27 18:52 ` Stephen Hemminger
2017-02-27 18:55 ` Stephen Hemminger
2017-02-28 20:19 ` Zaboj Campula
2017-02-28 21:47 ` Jiri Pirko
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=1488484288.5717.1.camel@post.cz \
--to=zaboj.campula@post$(echo .)cz \
--cc=jbenc@redhat$(echo .)com \
--cc=jiri@resnulli$(echo .)us \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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