summaryrefslogtreecommitdiffstats
path: root/net/mpls/internal.h
diff options
context:
space:
mode:
authorEric W. Biederman <ebiederm@xmission.com>2015-03-03 19:12:40 -0600
committerDavid S. Miller <davem@davemloft.net>2015-03-04 00:26:06 -0500
commita2519929aba78e8cec7955d2c2a0c1e230d1f6e6 (patch)
tree3e27a41694e69fef7edc45647cb80cd96742de65 /net/mpls/internal.h
parent7720c01f3f590116882e251f13c7e1d5602f8643 (diff)
downloadlinux-a2519929aba78e8cec7955d2c2a0c1e230d1f6e6.tar.gz
linux-a2519929aba78e8cec7955d2c2a0c1e230d1f6e6.tar.bz2
linux-a2519929aba78e8cec7955d2c2a0c1e230d1f6e6.zip
mpls: Basic support for adding and removing routes
mpls_route_add and mpls_route_del implement the basic logic for adding and removing Next Hop Label Forwarding Entries from the MPLS input label map. The addition and subtraction is done in a way that is consistent with how the existing routing table in Linux are maintained. Thus all of the work to deal with NLM_F_APPEND, NLM_F_EXCL, NLM_F_REPLACE, and NLM_F_CREATE. Cases that are not clearly defined such as changing the interpretation of the mpls reserved labels is not allowed. Because it seems like the right thing to do adding an MPLS route without specifying an input label and allowing the kernel to pick a free label table entry is supported. The implementation is currently less than optimal but that can be changed. As I don't have anything else to test with only ethernet and the loopback device are the only two device types currently supported for forwarding MPLS over. Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/mpls/internal.h')
0 files changed, 0 insertions, 0 deletions