[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5502E544.7030003@cumulusnetworks.com>
Date: Fri, 13 Mar 2015 06:25:24 -0700
From: roopa <roopa@...ulusnetworks.com>
To: David Miller <davem@...emloft.net>
CC: sfeldma@...il.com, jiri@...nulli.us, netdev@...r.kernel.org
Subject: Re: [PATCH net-next v2 0/3] switchdev: support stp updates on stacked
netdevices
On 3/12/15, 9:10 PM, David Miller wrote:
> From: roopa@...ulusnetworks.com
> Date: Thu, 12 Mar 2015 17:29:55 -0700
>
>> From: Roopa Prabhu <roopa@...ulusnetworks.com>
>>
>> This series moves bridge stp update api to follow the setlink/dellink
>> apis to propagate stp state updates to switch ports on stacked netdevs
>>
>> v1 -> v2:
>> fix comment
>> add CONFIG_NET_SWITCHDEV checks
>>
>> Signed-off-by: Roopa Prabhu <roopa@...ulusnetworks.com>
> Can't we just do this stacked device traveral transparently?
>
> That seems much cleaner to me.
David, if you mean not touch bond and team but have the switchdev api do
it transparently, yes, i had it that way initially.
And i do liked it that way as well. But the feedback i received (during
the initial introduction of this for setlink/dellink) was to make it
explicit for each master.
Thanks,
Roopa
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists