Thread (51 messages) 51 messages, 11 authors, 2015-03-30

Re: [PATCH net-next RFC v2] switchdev: bridge: drop hardware forwarded packets

From: Jiri Pirko <jiri@resnulli.us>
Date: 2015-03-27 07:01:06

Fri, Mar 27, 2015 at 07:43:35AM CET, sfeldma@gmail.com wrote:
On Thu, Mar 26, 2015 at 7:49 AM, Jiri Pirko [off-list ref] wrote:
quoted
Thu, Mar 26, 2015 at 03:28:28PM CET, sfeldma@gmail.com wrote:
quoted
quoted
What is the argument for not allowing stacked version of swdev_parent_id_get()?
That was suppose wo identify a switch port. "ip link" will show you that
and you see right away what is going on. If bond implements that, that
brigs a mess. I don't like that.
A bond is an aggregator of ports and showing switch_id for bond is no
more messy than showing link speed for bond, derived from link speed
on member ports.
Well, I don't think so. I think the switchid should be showed on port
devices only.

Please remind me why exactly you need this?

Also should switch id be showed on other devices? Like bridges, vlans,
macvlans, etc?
For bond it sometimes will be shown (2ports of the same switch)
sometimes not (2ports each of the different switch).
That looks messy to me. I might be wrong of course...

Jiri
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help