net: change bridge/macvlan hook to be be generic
Subsystems (3)
RFC 1/1 net: change bridge/macvlan hook to be be generic
The existing macvlan and bridge have special hooks in the packet input path. This patch changes it to a generic hook chain, like the packet type processing. I have been wanting to look into flow based switching, etc...
Pro: generic code rather than special purpose
safer against race during insertion/removal
easier for out of tree network code
Con: performance (loop vs unrolled) and calling module for each packet
easier for out of tree network code
This is prototype only, don't use it as is...
--- drivers/net/macvlan.c | 24 ++++++---- include/linux/netdevice.h | 19 ++++++++ net/bridge/br.c | 4 - net/bridge/br_fdb.c | 5 ++ net/bridge/br_input.c | 25 ++++++++-- net/bridge/br_private.h | 3 - net/core/dev.c | 107 +++++++++++++++++----------------------------- 7 files changed, 103 insertions(+), 84 deletions(-)
drivers/net/macvlan.c +16 -8
@@ -145,21 +145,24 @@ static void macvlan_broadcast(struct sk_ }/* called under rcu_read_lock() from netif_receive_skb */ -static struct sk_buff *macvlan_handle_frame (struct sk_buff *skb) +static struct sk_buff *macvlan_handle_frame (struct net_device *orig_dev, +struct sk_buff *skb) { -const struct ethhdr *eth =eth_hdr (skb); +const struct ethhdr *eth;const struct macvlan_port *port;const struct macvlan_dev *vlan; -const struct macvlan_dev *src;struct net_device *dev;unsigned int len; - port =rcu_dereference (skb->dev->macvlan_port); + port =rcu_dereference (orig_dev->macvlan_port);if (port ==NULL )return skb; + eth =eth_hdr (skb);if (is_multicast_ether_addr (eth->h_dest)) { - src =macvlan_hash_lookup (port, eth->h_source); +const struct macvlan_dev *src + =macvlan_hash_lookup (port, eth->h_source); +if (!src)/* frame comes from an external address */ macvlan_broadcast(skb, port, NULL,
@@ -759,19 +762,24 @@ static struct notifier_block macvlan_not .notifier_call = macvlan_device_event, }; +static struct packet_handler macvlan_hook = { + .priority =MACVLAN_HANDLER , + .func = macvlan_handle_frame, +}; +static int __init macvlan_init_module (void ) {int err;register_netdevice_notifier (&macvlan_notifier_block); - macvlan_handle_frame_hook = macvlan_handle_frame; err =macvlan_link_register (&macvlan_link_ops);if (err <0 ) goto err1; + +dev_add_handler (&macvlan_hook);return 0 ; err1: - macvlan_handle_frame_hook =NULL ;unregister_netdevice_notifier (&macvlan_notifier_block);return err; }
@@ -779,7 +787,7 @@ err1: static void __exit macvlan_cleanup_module(void) {rtnl_link_unregister (&macvlan_link_ops); - macvlan_handle_frame_hook =NULL ; +dev_remove_handler (&macvlan_hook);unregister_netdevice_notifier (&macvlan_notifier_block); }
include/linux/netdevice.h +19 -0
@@ -1011,10 +1011,15 @@ struct net_device {/* mid-layer private */ void *ml_priv; + +#if defined(CONFIG_BRIDGE ) || defined (CONFIG_BRIDGE_MODULE )/* bridge stuff */ struct net_bridge_port *br_port; +#endif +#if defined(CONFIG_MACVLAN ) || defined(CONFIG_MACVLAN_MODULE )/* macvlan */ struct macvlan_port *macvlan_port; +#endif /* GARP */ struct garp_port *garp_port;
@@ -1204,6 +1209,17 @@ struct packet_type {struct list_head list; }; +enum handler_priority { +BRIDGE_HANDLER =1 , +MACVLAN_HANDLER , +}; + +struct packet_handler { +struct list_head list; +enum handler_priority priority; +struct sk_buff * (*func)(struct net_device *,struct sk_buff *); +}; +#include <linux/interrupt.h> #include <linux/notifier.h>
@@ -1259,6 +1275,9 @@ extern void dev_add_pack(struct packet_extern void dev_remove_pack (struct packet_type *pt);extern void __dev_remove_pack (struct packet_type *pt); +extern void dev_add_handler (struct packet_handler *h); +extern void dev_remove_handler (struct packet_handler *h); +extern struct net_device *dev_get_by_flags (struct net *net,unsigned short flags,unsigned short mask);extern struct net_device *dev_get_by_name (struct net *net,const char *name);
net/bridge/br.c +2 -2
@@ -63,7 +63,7 @@ static int __init br_init(void) goto err_out4;brioctl_set (br_ioctl_deviceless_stub); - br_handle_frame_hook = br_handle_frame; +dev_add_handler (&br_packet_hook);#if defined(CONFIG_ATM_LANE ) || defined(CONFIG_ATM_LANE_MODULE ) br_fdb_test_addr_hook = br_fdb_test_addr;
@@ -100,7 +100,7 @@ static void __exit br_deinit(void) br_fdb_test_addr_hook =NULL ;#endif - br_handle_frame_hook =NULL ; +dev_remove_handler (&br_packet_hook);br_fdb_fini (); }
net/bridge/br_fdb.c +5 -0
@@ -253,6 +253,11 @@ int br_fdb_test_addr(struct net_device * return ret; } + +/* This hook is defined here for ATM LANE */ +int (*br_fdb_test_addr_hook)(struct net_device *dev, +unsigned char *addr)__read_mostly ; +EXPORT_SYMBOL_GPL (br_fdb_test_addr_hook);#endif /* CONFIG_ATM_LANE */ /*
net/bridge/br_input.c +19 -6
@@ -133,13 +133,19 @@ static inline int is_link_local(const un/* * Called via br_handle_frame_hook. * Return NULL if skb is handled -* note: already called with rcu_read_lock (preempt_disabled) +* note: already called with rcu_read_lock */ -struct sk_buff *br_handle_frame (struct net_bridge_port *p,struct sk_buff *skb) +static struct sk_buff *br_handle_frame (struct net_device *dev, +struct sk_buff *skb) { -const unsigned char *dest =eth_hdr (skb)->h_dest; +const unsigned char *dest; +struct net_bridge_port *port;int (*rhook)(struct sk_buff *skb); +if (skb->pkt_type ==PACKET_LOOPBACK || + (port =rcu_dereference (skb->dev->br_port)) ==NULL ) +return skb; +if (!is_valid_ether_addr (eth_hdr (skb)->h_source)) goto drop;
@@ -147,13 +153,14 @@ struct sk_buff *br_handle_frame(struct nif (!skb)return NULL ; + dest =eth_hdr (skb)->h_dest;if (unlikely (is_link_local (dest))) {/* Pause frames shouldn't be passed up by driver anyway */ if (skb->protocol ==htons (ETH_P_PAUSE )) goto drop;/* If STP is turned off, then forward */ -if (p->br->stp_enabled ==BR_NO_STP && dest[5 ] ==0 ) +if (port->br->stp_enabled ==BR_NO_STP && dest[5 ] ==0 ) goto forward; if (NF_HOOK(PF_BRIDGE, NF_BR_LOCAL_IN, skb, skb->dev,
@@ -164,7 +171,7 @@ struct sk_buff *br_handle_frame(struct n } forward: -switch (p->state) { +switch (port->state) {case BR_STATE_FORWARDING : rhook =rcu_dereference (br_should_route_hook);if (rhook !=NULL ) {
@@ -174,7 +181,7 @@ forward: }/* fall through */ case BR_STATE_LEARNING : -if (!compare_ether_addr (p->br->dev->dev_addr, dest)) +if (!compare_ether_addr (port->br->dev->dev_addr, dest)) skb->pkt_type =PACKET_HOST ; NF_HOOK(PF_BRIDGE, NF_BR_PRE_ROUTING, skb, skb->dev, NULL,
@@ -186,3 +193,9 @@ drop: }return NULL ; } + +struct packet_handler br_packet_hook = { + .priority =BRIDGE_HANDLER , + .func = br_handle_frame, +}; +
net/bridge/br_private.h +1 -2
@@ -300,8 +300,7 @@ extern void br_features_recompute(struct/* br_input.c */ extern int br_handle_frame_finish (struct sk_buff *skb); -extern struct sk_buff *br_handle_frame (struct net_bridge_port *p, -struct sk_buff *skb); +extern struct packet_handler br_packet_hook;/* br_ioctl.c */ extern int br_dev_ioctl (struct net_device *dev,struct ifreq *rq,int cmd);
net/core/dev.c +41 -66
150 lines not on this page · raw message
Quoted 3 lines · Stephen Hemminger
The existing macvlan and bridge have special hooks in the packet input path. This patch changes it to a generic hook chain, like the packet type processing. I have been wanting to look into flow based switching, etc...
Can this be further simplified by saying that a netdev can only be hooked by one mux (macvlan, bridge, etc) at any given time, so there is never more than one element in the hook chain. If so, then we just need a single hook, not a chain.
It seems odd to me that a dev would have both macvlan_port != NULL and br_port != NULL. Can dev be in a macvlan and a bridge at the same time?
-scott
Quoted 6 lines · Scott Feldman
Quoted 3 lines · Stephen Hemminger
The existing macvlan and bridge have special hooks in the packet input path. This patch changes it to a generic hook chain, like the packet type processing. I have been wanting to look into flow based switching, etc...
Quoted 7 lines
Can this be further simplified by saying that a netdev can only be hooked by one mux (macvlan, bridge, etc) at any given time, so there is never more than one element in the hook chain. If so, then we just need a single hook, not a chain.
It seems odd to me that a dev would have both
macvlan_port!= NULL andbr_port!= NULL. Can dev be in a macvlan and a bridge at the same time?
Yes, its possible to use the ebtables broute table to have packets selectively delivered upwards in the stack instead of briding them. "upwards" could also mean to a macvlan device.
I don't know if anyone is actually doing this, but its a configuration which currently should work.
Quoted 6 lines · Scott Feldman
Quoted 3 lines · Stephen Hemminger
The existing macvlan and bridge have special hooks in the packet input path. This patch changes it to a generic hook chain, like the packet type processing. I have been wanting to look into flow based switching, etc...
Quoted 7 lines
Can this be further simplified by saying that a netdev can only be hooked by one mux (macvlan, bridge, etc) at any given time, so there is never more than one element in the hook chain. If so, then we just need a single hook, not a chain.
It seems odd to me that a dev would have both
macvlan_port!= NULL andbr_port!= NULL. Can dev be in a macvlan and a bridge at the same time?
If we did add the generic hook list, then we could support other hooks, like a pktgen rx hook to gather latency, pkt-loss, and similar stats, for example.
Thanks,
Ben
Signature · 2 lines
Ben Greear <[email protected]> Candela Technologies Inc http://www.candelatech.com