diff options
| author |   Ido Schimmel <idosch@mellanox.com> | 2017-02-06 16:20:11 +0100 |
|---|---|---|
| committer |   David S. Miller <davem@davemloft.net> | 2017-02-06 11:25:56 -0500 |
| commit | e60234ddb541b556b57353dfddca73155977d02f (patch) | |
| tree | 3a213f381a257e396861af789bb87d31adb387f4 /net | |
| parent | mlxsw: core: Queue work immediately instead of delaying it (diff) | |
| download | linux-dev-e60234ddb541b556b57353dfddca73155977d02f.tar.xz linux-dev-e60234ddb541b556b57353dfddca73155977d02f.zip | |
mlxsw: spectrum_router: Use ordered workqueue for neigh updates
We currently associate each neighbour entry with a work item, so it's
not possible to have multiple events queued for the same neighbour
entry. However, this is about to be changed so that the neighbour entry
is only resolved when the work item is scheduled.
The above can result in a mismatch between the kernel's and the device's
neighbour table, unless the associated work items are processed in the
order in which they were submitted.
Do that by migrating the NEIGH_UPDATE work items to be processed in the
ordered workqueue which was recently introduced in mlxsw in commit
a3832b31898f ("mlxsw: core: Create an ordered workqueue for FIB
offload").
Signed-off-by: Ido Schimmel <idosch@mellanox.com>
Signed-off-by: Jiri Pirko <jiri@mellanox.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions