Commit aa05b988 authored by Andy Gospodarek's avatar Andy Gospodarek Committed by Stephen Hemminger

iproute2: unify naming for entries offloaded to hardware

The kernel now has the capability to offload FDB and FIB entries to hardware.
It is important to let users know if table entries are also offloaded to
hardware.  Currently offloaded FDB entries are indicated by the existence of
the flag 'external' on the entry as of the following commit:

commit 28467b7f
Author: Scott Feldman <sfeldma@gmail.com>
Date:   Thu Dec 4 09:57:15 2014 +0100

    bridge/fdb: add flag/indication for FDB entry synced from offload device

When the patch to add support for indicating that FIB entries were also
offloaded as posted to netdev by Scott Feldman it became clear that 'external'
would not be an ideal name for routes.  There could definitely be confusion
about what this might mean since many routes are to external networks -- a
collision/confusion that did not happen with FDB.

Scott Feldman asked me to check with others and build concensus around a name.
After speaking with several people about this I am proposing we refer to both
FDB and FIB entries that are currently backed by hardware (based on the work
done in rocker) with the flag 'offload' appended to the end ofthe entry.

Some people liked the string 'external,' others liked 'hardware,' but the point
is to communicate that these routes are available to something that will will
offload the forwarding normally done by the kernel.  Since the term 'offload'
is used so frequently it seems appropriate to use the same language in
ip/bridge output.

The term 'offload' also seems to resonate with many of the people who have
responded on Scott's original thread or to those who I reached out to directly
and did respond to my query, so it seems we have reached consensus that it
should be the term used going forward.

v2: rebased against net-next branch
Signed-off-by: default avatarAndy Gospodarek <gospo@cumulusnetworks.com>
CC: Jamal Hadi Salim <jhs@mojatatu.com>
CC: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
CC: Jiri Pirko <jiri@resnulli.us>
CC: John W. Linville <linville@tuxdriver.com>
CC: Roopa Prabhu <roopa@cumulusnetworks.com>
CC: Scott Feldman <sfeldma@gmail.com>
CC: Stephen Hemminger <stephen@networkplumber.org>
parent 93531fac
...@@ -159,7 +159,7 @@ int print_fdb(const struct sockaddr_nl *who, struct nlmsghdr *n, void *arg) ...@@ -159,7 +159,7 @@ int print_fdb(const struct sockaddr_nl *who, struct nlmsghdr *n, void *arg)
if (r->ndm_flags & NTF_ROUTER) if (r->ndm_flags & NTF_ROUTER)
fprintf(fp, "router "); fprintf(fp, "router ");
if (r->ndm_flags & NTF_EXT_LEARNED) if (r->ndm_flags & NTF_EXT_LEARNED)
fprintf(fp, "external "); fprintf(fp, "offload ");
fprintf(fp, "%s\n", state_n2a(r->ndm_state)); fprintf(fp, "%s\n", state_n2a(r->ndm_state));
return 0; return 0;
......
...@@ -448,7 +448,7 @@ int print_route(const struct sockaddr_nl *who, struct nlmsghdr *n, void *arg) ...@@ -448,7 +448,7 @@ int print_route(const struct sockaddr_nl *who, struct nlmsghdr *n, void *arg)
if (r->rtm_flags & RTNH_F_PERVASIVE) if (r->rtm_flags & RTNH_F_PERVASIVE)
fprintf(fp, "pervasive "); fprintf(fp, "pervasive ");
if (r->rtm_flags & RTNH_F_EXTERNAL) if (r->rtm_flags & RTNH_F_EXTERNAL)
fprintf(fp, "external "); fprintf(fp, "offload ");
if (r->rtm_flags & RTM_F_NOTIFY) if (r->rtm_flags & RTM_F_NOTIFY)
fprintf(fp, "notify "); fprintf(fp, "notify ");
if (tb[RTA_MARK]) { if (tb[RTA_MARK]) {
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment