linux_dsm_epyc7002/include/net/netns/nexthop.h

/* SPDX-License-Identifier: GPL-2.0 */
/*
 * nexthops in net namespaces
 */

#ifndef __NETNS_NEXTHOP_H__
#define __NETNS_NEXTHOP_H__

#include <linux/rbtree.h>

struct netns_nexthop {
	struct rb_root		rb_root;	/* tree of nexthops by id */
	struct hlist_head	*devhash;	/* nexthops by device */

	unsigned int		seq;		/* protected by rtnl_mutex */
	u32			last_id_allocated;
	struct blocking_notifier_head notifier_chain;
};
#endif
net: Initial nexthop code Barebones start point for nexthops. Implementation for RTM commands, notifications, management of rbtree for holding nexthops by id, and kernel side data structures for nexthops and nexthop config. Nexthops are maintained in an rbtree sorted by id. Similar to routes, nexthops are configured per namespace using netns_nexthop struct added to struct net. Nexthop notifications are sent when a nexthop is added or deleted, but NOT if the delete is due to a device event or network namespace teardown (which also involves device events). Applications are expected to use the device down event to flush nexthops and any routes used by the nexthops. Signed-off-by: David Ahern <dsahern@gmail.com> Signed-off-by: David S. Miller <davem@davemloft.net> 2019-05-25 04:43:04 +07:00			`/* SPDX-License-Identifier: GPL-2.0 */`
			`/*`
			`* nexthops in net namespaces`
			`*/`

			`#ifndef __NETNS_NEXTHOP_H__`
			`#define __NETNS_NEXTHOP_H__`

			`#include <linux/rbtree.h>`

			`struct netns_nexthop {`
			`struct rb_root rb_root; /* tree of nexthops by id */`
			`struct hlist_head devhash; / nexthops by device */`

			`unsigned int seq; /* protected by rtnl_mutex */`
			`u32 last_id_allocated;`
nexthop: Convert to blocking notification chain Currently, the only listener of the nexthop notification chain is the VXLAN driver. Subsequent patches will add more listeners (e.g., device drivers such as netdevsim) that need to be able to block when processing notifications. Therefore, convert the notification chain to a blocking one. This is safe as notifications are always emitted from process context. Signed-off-by: Ido Schimmel <idosch@nvidia.com> Reviewed-by: David Ahern <dsahern@gmail.com> Signed-off-by: David S. Miller <davem@davemloft.net> 2020-09-15 18:41:01 +07:00			`struct blocking_notifier_head notifier_chain;`
net: Initial nexthop code Barebones start point for nexthops. Implementation for RTM commands, notifications, management of rbtree for holding nexthops by id, and kernel side data structures for nexthops and nexthop config. Nexthops are maintained in an rbtree sorted by id. Similar to routes, nexthops are configured per namespace using netns_nexthop struct added to struct net. Nexthop notifications are sent when a nexthop is added or deleted, but NOT if the delete is due to a device event or network namespace teardown (which also involves device events). Applications are expected to use the device down event to flush nexthops and any routes used by the nexthops. Signed-off-by: David Ahern <dsahern@gmail.com> Signed-off-by: David S. Miller <davem@davemloft.net> 2019-05-25 04:43:04 +07:00			`};`
			`#endif`