Re: [patch net-next 00/26] bonding/team offload + mlxsw implementation

Or Gerlitz
2015-12-01T16:35:44Z

On Tue, Dec 1, 2015 at 5:12 PM, Jiri Pirko <jiri@resnulli.us> wrote:
> Tue, Dec 01, 2015 at 04:06:23PM CET, gerlitz.or@gmail.com wrote:
>>On Tue, Dec 1, 2015 at 4:43 PM, Jiri Pirko <jiri@resnulli.us> wrote:
>>> Tue, Dec 01, 2015 at 02:48:38PM CET, jiri@resnulli.us wrote:

>>>>This patchset introduces needed infrastructure for link aggregation
>>>>offload - for both team and bonding. It also implements the offload
>>>>in mlxsw driver.

>>I didn't see any changes to switchdev.h, can you elaborate on that please.

> Correct. This patchset does not extend switchdev api. The extension is
> done for netdev notifiers. It seems natural and correct.
> As we discussed already with John on a different thread, it makes sense
> for non-switchdev drivers to benefit from this extensions as well.

This is understood.

However, the point which is still not clear to me related to the LAG /
switchdev object model.

All of FDB/VLAN/FIB switchdev objects have corresponding software counterparts
in the kernel --- what's the case for LAG? the software construct is
bond or team
instance, shouldn't there be a modeling of the HW LAG object in switchdev?

Or.