diff options
| author | Ido Schimmel <idosch@nvidia.com> | 2020-11-04 15:30:29 +0200 |
|---|---|---|
| committer | Jakub Kicinski <kuba@kernel.org> | 2020-11-06 11:28:49 -0800 |
| commit | 732d167bf5f53a8c1e8c53cf7dbffe2a13f63752 (patch) | |
| tree | 790ade2d34897b86daa9a9ebf854975afdfbe201 /ipc | |
| parent | e95f2592f633a334b175003f13f42d3c217dc657 (diff) | |
| download | linux-stable-732d167bf5f53a8c1e8c53cf7dbffe2a13f63752.tar.gz linux-stable-732d167bf5f53a8c1e8c53cf7dbffe2a13f63752.tar.bz2 linux-stable-732d167bf5f53a8c1e8c53cf7dbffe2a13f63752.zip | |
nexthop: Emit a notification when a nexthop is added
Emit a notification in the nexthop notification chain when a new nexthop
is added (not replaced). The nexthop can either be a new group or a
single nexthop.
The notification is sent after the nexthop is inserted into the
red-black tree, as listeners might need to callback into the nexthop
code with the nexthop ID in order to mark the nexthop as offloaded.
A 'REPLACE' notification is emitted instead of 'ADD' as the distinction
between the two is not important for in-kernel listeners. In case the
listener is not familiar with the encoded nexthop ID, it can simply
treat it as a new one. This is also consistent with the route offload
API.
Changes since RFC:
* Reword commit message
Signed-off-by: Ido Schimmel <idosch@nvidia.com>
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'ipc')
0 files changed, 0 insertions, 0 deletions