[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20160705.091043.970062018694402093.davem@davemloft.net>
Date: Tue, 05 Jul 2016 09:10:43 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: jiri@...nulli.us
Cc: netdev@...r.kernel.org, idosch@...lanox.com, yotamg@...lanox.com,
eladr@...lanox.com, nogahf@...lanox.com, ogerlitz@...lanox.com,
sfeldma@...il.com, roopa@...ulusnetworks.com, andy@...yhouse.net,
dsa@...ulusnetworks.com, tgraf@...g.ch, jhs@...atatu.com,
linville@...driver.com, ivecera@...hat.com
Subject: Re: [patch net-next 00/16] mlxsw: Implement IPV4 unicast routing
From: Jiri Pirko <jiri@...nulli.us>
Date: Tue, 5 Jul 2016 11:27:36 +0200
> This patchset enables IPv4 unicast routing in the Mellanox Spectrum ASIC
> switch driver. This builds upon the work that was done by a couple of
> previous patchsets.
>
> Patches 1,2,6 add a couple of dependencies outside the driver. Namely, the
> ability to propagate ndo_neigh_construct()/destroy() through stacked devices and
> a notification whenever DELAY_PROBE_TIME changes. When propagated down, the
> ndos allow drivers to add and remove neighbour entries from their private
> neighbour table. The DELAY_PROBE_TIME notification gives drivers the ability to
> correctly configure their polling interval for neighbour activity, so that
> active neighbour won't be marked as STALE.
>
> Patches 3-5,7-8 add the neighbour offloading infrastructure, where patch 7 uses
> the DELAY_PROBE_TIME notification in order to correctly configure the device's
> polling interval. Patch 8 finally programs neighbours to the device's table
> based on NEIGH_UPDATE notifications, so that directly connected routes can
> be used.
>
> Patches 9-16 build upon the previous patches and extend the router with
> remote routes (nexthop) support.
Looks good to me, series applied, thanks Jiri!
Powered by blists - more mailing lists