diff options
| author | Petr Machata <[email protected]> | 2021-03-26 14:20:22 +0100 |
|---|---|---|
| committer | David S. Miller <[email protected]> | 2021-03-28 17:53:39 -0700 |
| commit | de1d1ee3e3e9f028623e7beb4c090a2b68572f10 (patch) | |
| tree | 7476abb7e8aa3d785b604141eb37745e0279bda1 /tools/perf/scripts/python/bin/export-to-postgresql-report | |
| parent | 9195f06b2d0fd0d1cc1552970d890c21f6b9492f (diff) | |
nexthop: Rename artifacts related to legacy multipath nexthop groups
After resilient next-hop groups have been added recently, there are two
types of multipath next-hop groups: the legacy "mpath", and the new
"resilient". Calling the legacy next-hop group type "mpath" is unfortunate,
because that describes the fact that a packet could be forwarded in one of
several paths, which is also true for the resilient next-hop groups.
Therefore, to make the naming clearer, rename various artifacts to reflect
the assumptions made. Therefore as of this patch:
- The flag for multipath groups is nh_grp_entry::is_multipath. This
includes the legacy and resilient groups, as well as any future group
types that behave as multipath groups.
Functions that assume this have "mpath" in the name.
- The flag for legacy multipath groups is nh_grp_entry::hash_threshold.
Functions that assume this have "hthr" in the name.
- The flag for resilient groups is nh_grp_entry::resilient.
Functions that assume this have "res" in the name.
Besides the above, struct nh_grp_entry::mpath was renamed to ::hthr as
well.
UAPI artifacts were obviously left intact.
Suggested-by: David Ahern <[email protected]>
Signed-off-by: Petr Machata <[email protected]>
Reviewed-by: David Ahern <[email protected]>
Signed-off-by: David S. Miller <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin/export-to-postgresql-report')
0 files changed, 0 insertions, 0 deletions