/* * Copyright (C) 2013-2014 Renesas Electronics Europe Ltd. * Author: Guennadi Liakhovetski * * This program is free software; you can redistribute it and/or modify * it under the terms of version 2 of the GNU General Public License as * published by the Free Software Foundation. */ #ifndef DT_BINDINGS_NBPFAXI_H #define DT_BINDINGS_NBPFAXI_H /** * Use "#dma-cells = <2>;" with the second integer defining slave DMA flags: */ #define NBPF_SLAVE_RQ_HIGH 1 #define NBPF_SLAVE_RQ_LOW 2 #define NBPF_SLAVE_RQ_LEVEL 4 #endif id='cgit'>

summary refs log tree commit diff

path: root/include/net/netlink.h

Age	Commit message (Collapse)	Author	Files	Lines
2017-02-04	net: ipv6: Change notifications for multipath add to RTA_MULTIPATH	David Ahern	1	-0/+1
	Change ip6_route_multipath_add to send one notifciation with the full route encoded with RTA_MULTIPATH instead of a series of individual routes. This is done by adding a skip_notify flag to the nl_info struct. The flag is used to skip sending of the notification in the fib code that actually inserts the route. Once the full route has been added, a notification is generated with all nexthops. ip6_route_multipath_add handles 3 use cases: new routes, route replace, and route append. The multipath notification generated needs to be consistent with the order of the nexthops and it should be consistent with the order in a FIB dump which means the route with the first nexthop needs to be used as the route reference. For the first 2 cases (new and replace), a reference to the route used to send the notification is obtained by saving the first route added. For the append case, the last route added is used to loop back to its first sibling route which is the first nexthop in the multipath route. Signed-off-by: David Ahern <dsa@cumulusnetworks.com> Signed-off-by: David S. Miller <davem@davemloft.net>